Category: Business Analysts
Part 5 of 6 in the “Double the Value in Half the Time” series based on David Hawks’ presentation from Keep Austin Agile 2015. Stay tuned for subsequent posts…
The fifth problem… we’re not getting things done. This is the Scrumbut part of Scrum. “Yeah, we do Scrum but we carry over stuff every sprint. The work just doesn’t fit in two weeks.” We have to figure how to break work down so it can be finished in a sprint. If not, we’re not getting to done and we’re not getting that potentially shippable product increment.
Product Owners typically express application requirements from a user-centric perspective. This usually means that non-functional requirements are not a primary focus. However, Product Owners often forget that they and the development team are also potentially a class of “user” of features in the application being developed. The PO and team might want features to help with maintenance and debugging, or with helping to determine how the system is being used. With this in mind, here is a quick list of some non-functional stories that POs often overlook:
Part 2 of 6 in the “Double the Value in Half the Time” series based on David Hawks’ presentation from Keep Austin Agile 2015. Stay tuned for subsequent posts…
The second problem in the “Deliver Double the Value in Half the Time” series is that the Team doesn’t have a shared understanding of their purpose.
Many of us have lived in a world of three false assumptions:
- The customer knows what she wants
- The developers know how to build it
- Nothing will change along the way
What is the role of the agile business analyst? In this presentation to the Austin IIBA chapter, David Hawks talks about:
- What are iterative requirements and how to do them
- What are the roles of the product owner and how does the business analyst relate
- How to create user stories
- Incremental and iterative evolution of a story
- Explanation of backlog physics