Joint Application Modeling®
The Stream Process™ for Government
Working with the federal government brings new challenges to gathering and documenting software requirements. We continue to evolve our novel approach to software requirements and have modified it to address the unique needs government projects.
The fundamental problem with the way software project requirements are gathered and documented in the government is the lack of Clarity. Stakeholders don't really know what they want until they see and interact with it.
Our approach allow stakeholders to experience ideas that often never see the light of day due to the typical challenges every company faces - vision clarity, project re-work, ambiguous requirements, and missed milestones (to name just a few). Typically, a concept can be brought to life in a matter of days, instead of weeks or months, where programming is involved.
"That" Meeting
You've been in that meeting where stakeholders talk about what they want, debate features, and maybe even have an argument or two. A few weeks or months later, someone sends out a hefty document to read and approve.
Most of the time, what was captured in the document is not exactly what was discussed. Notes and textual requirements can be ambiguous and it's easy to miss details. More importantly, during the meeting all participants had a unique vision of what the project would look like. This is the low end of what we call the Requirements Clarity Gap.
The JAM Session®
Imagine this: everyone walks out of the meeting with a shared vision for the project. Collaboration and communication have been enhanced and requirements were captured and agreed upon in real time.
We call it a JAM Session® (Joint Application Modeling® Session), and it's a core component of our Stream Process™. During a JAM Session, stakeholders see their requirements come to life. They experience the project before the development team writes a single line of code. And everyone leaves the session with a common vision for the project.
In fact, while each project is unique, our approach has reduced requirements-related defects by half and saved overall project costs by up to 50%. The requirements phase typically costs 20%-30% of a project. We have brought that down as low as 1%. We have also helped to launch projects up to 35% faster and with more features than when following a traditional requirements process.
If you're ready to get started, contact us today!
