Presented by Appian
Delivering software faster begins with a clear understanding of the mission and a requirements owner who stays involved. John Hinnant, Chief of Munitions, U.S. Army, and Jonathan Mappin, Account Executive, Army (DoD), Appian, describe how that combination is helping the Army modernize the systems supporting munitions planning and management.
In a Fed Gov Today Spotlight recorded at Appian Government, they explain a partnership focused on a practical objective: helping units obtain the right munitions where and when they need them.
Hinnant emphasizes the ability to turn functional requirements into usable capabilities quickly. He wants his team focused on the work the Army must accomplish, with software supporting that work rather than becoming an obstacle.
That relationship helps clarify priorities and resolve questions as the system takes shape. Requirements become part of an ongoing conversation about how the application should function, rather than a document separated from implementation.
Hinnant brings decades of experience across the munitions enterprise. He describes work involving users, logistics, production, and requirements. That background helps him recognize where existing processes create problems and explain what the replacement needs to improve.
He also acknowledges the effort required to stay involved. His office has other responsibilities and limited dedicated staff. Personal attention to the project becomes a way to maintain momentum and keep the focus on the capability units need.
The modernization effort replaces an older system used for requirements, authorizations, forecasting, requests, and expenditures. Hinnant says the new system’s identity also needs to communicate that its responsibilities include combat needs as well as training.
He describes reaching initial capability in roughly 160 days from the start of the development effort. The emphasis is on an initial operational capability that users can begin applying while the team continues building.
Mappin links that speed to a platform and delivery approach that bring functional owners and developers into a shared understanding of the application. A graphical view can help mission experts participate without requiring them to become software developers.
Feedback continues after deployment. Hinnant describes demonstrations, live use, and responses from users as ways to assess whether the capability is working. Positive feedback helps validate the approach; problems become inputs for correction.
That approach changes the meaning of completion. Deployment is a milestone in an ongoing process of learning and adjustment, rather than the point at which software stops changing.
For other government modernization efforts, the example highlights the value of active mission ownership, direct collaboration, and usable increments. Speed comes from keeping decisions close to the people who understand the work and maintaining a feedback loop that carries their experience into the next release.
3 Key Takeaways