So your team has gone agile? But the ecosystem has not fully moved…You’re sprinting, but not sure what work is being developed…You need stories to sprint, but still getting a 100 page requirements document…You want quick decisions, but still have the approval processes…
You’ve won the RFP, you’ve hired your scrum team…everyone on the team is excited…The project is initiated, Sprint 0 is completed, and your team is ready to sprint…how does Sprint 1, 2, and 3 look like?
Did you experience broken sprint commitments? Did you have estimations that were off? Did you have misunderstanding of requirements? Did you struggle with roles and responsibilities?
The government ecosystem will not change overnight, and what must be understood is that accountability is still key in the government space — showing evidence of work and audibility of work and requirements.
At the end of this session, you will be able to understand how to use the Design Thinking Framework to take a requirements document and break it up into agile features and stories to create a roadmap on how you will deliver all that’s being asked. Specific techniques to be taught will include:
- User Personification
- Affinity Mapping
- Reason for vertical Slicing of Requirements
- What constitutes a good feature or user story
- Roadmap creation
Presentation session will include:
- Introduction to pain points and topic
- Design Thinking Framework
- Reason for creating vertical slices of requirements
- Why understanding user needs and pain points is important to creation of features
- My challenges of navigating my agile journey
- Close with key takeaways
Whether you’re a developer, tester, project manager, scrum master, or product owner, this session will benefit all who work in an environment who is transforming from traditional project management to agile management of work.