Requirements for Agile-Based Projects
Are you beginning to use Agile techniques and need guidance on how to best document requirements? Is your Agile process lacking in needed requirements discipline and documentation?
Agile techniques can quickly and efficiently deliver software, yet Agile development has its risks: lack of structure and documentation, insufficient software design, and an increased risk of scope creep, just to name a few. For organizations who are starting an Agile initiative or want to improve their existing techniques, we can provide business analysts who are trained in our Agile Model Driven Requirements methodology.
The approach builds on Agile techniques to deliver requirements iteratively with a goal to improving quality and reducing risk while meeting the needs of Agile development for speed and low overhead. At the core of the approach are UML models, a robust requirements tool, and a central repository. Through this combination, effective documentation and requirements specifications can be built at pace with Agile software development iterations.
The approach is characterized by four distinct phases which occur during each iteration. Iteration length will vary depending on feature complexity and an organization’s approach to Agile, but generally will be between 2-4 weeks.
Acquire: Collaborative techniques are used to gather information, build preliminary models, and define requirements.
Model: Models are built to describe the system.
Demonstrate: Work products are reviewed with a focus on team interaction and group problem solving with an end goal of green-lighting development.
Report: Requirements specifications and test scripts are generated automatically from the central repository for use during development and verification.
What work products can you expect?
- UML-based models for Agile iterations
- User stories
- Requirements documented in a repository
Contact us at 617-482-4444 and let us know how we can help your project.