Agile Estimation and Analysis for Developers and Product Owners
- How do I create my stories in the first place?
- How do I manage my analysis over the life of the project?
- How can I split up stories that are too complex to fit in an iteration?
- If I have many similar, but different stories, how do I make sure they are implemented in a similar way to avoid getting many special cases in my code?
- How does Agile analysis affect architecture?
- How do I coordinate the implementation of similar stories?
- How do I make sure I have all the stories I need?
- How can I ensure my stories are consistent with each other?
Agile analysis has brought about new challenges and new opportunities. Old-school techniques of heavy use-cases or significant up-front analysis no longer work effectively. But how can our requirements be managed effectively when many things are so unclear at the start of a project?
Agile Estimation and Analysis for Developers and Product Owners blends several technologies together in a breakthrough course that gives the tools the entire development team needs to uncover and manage the story definition/discovery process. Software development is most like product development. That is, much of it is about discovering what the customer wants and how to build it. Actually constructing the code is not the biggest problem.
This course focuses on uncovering and managing the customers’ needs of the product being built. It teaches how to discover the stories in an Agile manner. However, it goes beyond the process of merely pulling out stories as they are encountered. It also illustrates how to organize the stories so they can be more easily implemented in a consistent manner. Techniques on how to organize requirements to help insure consistent and complete information from your customers and/or subject matter experts (SMEs) are also presented.
This course also goes beyond the Agile mandate of prioritizing stories merely by customer value. It explains why the issues of risk mitigation and customer feedback opportunities must also be considered.
By bringing together project management, analysis, development, and QA issues to the role of requirements management in Agile projects, this course enables your staff to be more effective than standard Product Owner training available from other organizations.
Course Length
2 days
Course Level
IntermediateCourse Outline
- Lessons from Lean Software Development
- The Scientific Method
- Respect People
- Respect Knowledge
- Improving Process
- Wastes in Software Development
- Building what you don’t need
- Complexity
- Non-Maintainability
- Overview of Agile Methods
- Five Reasons to Go Agile
- Add Business Value Quickly
- Get Clarity on Customer Needs
- Project Management
- Help the Team
- Technical Perspective
- The Risks of Software Development
- Starting Analysis
- Background
- Use Cases and Why To Use Them
- How To Use Use Cases in an Agile Project
- Use Cases As Containers for Stories
- Creating Low Precision Use Cases From High Level Requirements Statements
- Use Case Unfolding
- Sub-Dividing Stories Into Smaller Stories
- The Relationship Between Analysis and Architecture
- How Stories Can be Related to Each Other
- Estimation in an Object-Oriented World
- Commonality-Variability Analysis
- The Analysis Matrix
- Identifying The Concepts in Your Domain
- Mapping Scenarios Into Stories
- Creating a Conceptual Architecture
- Why Just Jumping Into Code Is Not A Good Idea
- Story Boarding
- Selecting Stories for the Iteration
- Prioritization
- Risk Mitigation
- Increasing Feedback
- Stories and Testing
- The Role of QA in Analysis
- Refining Our Test Cases
- Agile Project Estimation
- Agile Story Estimation
- Kano Analysis
- The Changing Role of the Analyst
- Wastes in Analysis and How To Avoid Them
- Products Vs Projects