Manage Requirements in an Agile Environment
Agile and requirements management are complementary, not competitors.
Book This Workshop
A failure to find balance between Agile and requirements management can bring significant financial and non-financial impacts.
- Spending time, money, and effort reworking requirements that don’t quite satisfy your stakeholders.
- Confusion between various lines of business, or silos of the organization as to what is the “right” approach.
- A never ending cycle of poor requirements resulting in poor solutions and severely dissatisfied stakeholders.
Aligning your Agile and Requirements Management practices can deliver incredible business value.
- Improving team alignment and satisfaction.
- Clearly defining roles for project team members.
- Delivering solutions to your business partners that add value.
- Ensuring your documentation is just enough to enable work, now, and in the future.
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Book NowModule 1: Framing Agile and Business Analysis
The Purpose
Sets the context for the organization, to ensure a shared understanding of the benefits of both Agile and business analysis/requirements management.
Key Benefits Achieved
- Have a shared definition of Agile and business analysis / requirements.
- Understand the current state of Agile and business analysis in your organization.
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Define what Agile and business analysis mean in your organization. |
|
| 1.2 | Agile requirements assessment. |
|
Module 2: Tailoring Your Approach
The Purpose
Confirm you’re going the right way for effective solution delivery.
Key Benefits Achieved
Confirm the appropriate delivery methodology.
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Confirm your selected methodology. |
|
Module 3: Defining Your Requirements Thresholds
The Purpose
Provides the guardrails for your Agile requirements practice, to define a high-level process, roles and responsibilities, governance and decision-making, and how to deal with change.
Key Benefits Achieved
- Clearly defined interactions between the BA and their partners
- Define a plan for management and governance at the project team level
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Define your agile requirements process. |
|
| 3.2 | Define your agile requirements RACI. |
|
| 3.3 | Define your governance. |
|
| 3.4 | Define your change and backlog refinement plan. |
|
Module 4: Planning Your Next Steps
The Purpose
Provides the action plan to achieve your target state maturity
Key Benefits Achieved
- Recognize and prepare for the new ways of working for communication, stakeholder engagement, within the team, and across the organization.
- Establish a roadmap for next steps to mature your Agile requirements practice.
| Activities: | Outputs: | |
|---|---|---|
| 4.1 | Define your stakeholder communication plan. |
|
| 4.2 | Identify your capability gaps. |
|
| 4.3 | Plan your agile requirements roadmap. |
|
Module 5: Agile Requirements Techniques (Optional)
The Purpose
To provide practical guidance on technique usage, which can enable an improved experience with technical elements of the blueprint.
Key Benefits Achieved
- An opportunity to learn new tools to support your Agile requirements practice.
| Activities: | Outputs: | |
|---|---|---|
| 5.1 | Managing requirements' traceability. |
|
| 5.2 | Creating and managing user stories. |
|
| 5.3 | Managing your requirements backlog. |
|
| 5.4 | Maintaining a requirements library. |
|