Agile 101 provides the foundation for any technology or business professional who wants to become knowledgeable and skilled in the basics of agile. Participants will learn about the agile manifesto and how it informs the functioning of agile, contrasting key points with what they may be used to in waterfall development practices. Specific topics covered include the agile sprint cycle and what a shippable product is, the product owner, scrum master and development team roles, concepts including backlog creation and prioritization, iterative design, minimum viable product (MVP), definitions of done and ready (DOD, DOR), the estimation process, story points, team velocity, sprint retrospective and its’ role in the continuous improvement process, the agile view of releasing software, the customer feedback process, the distinction between and purpose of epics, stories, and acceptance criteria. Agile 101 is an excellent starting point for anyone considering or implementing an agile software development practice at their workplace.
- Introduction to agile
- The Agile Manifesto
- Basic agile Flow
- Core Roles in Agile
- Distinction between agile & waterfall practices
- Key Roles: Product Owner, Scrum Master, Developer
- Discussion of each role & how agile requires them all for good functioning
- What problems are introduced if they are missed.
- Sprint cycle using Scrum
- Components of the cycle (backlog, prioritization, development sprint, shippable product)
- Opportunities for continuous feedback for both the product and the team.
- Flexibility built into the system.
- Detailed sprint activities, ceremonies, rituals
- Sprint planning, standup, showcase, retrospective, estimation.
- Definitions of Done (DOD) and ready (DOR)
- Sprint integrity and why it is important
- Estimation, story points, velocity
- What are story points and how they are used
- Definition and understanding of velocity
- How estimation works and what the purpose is.
- Writing good stories, acceptance criteria, and story decomposition
- Story narrative form and why it’s important
- The purpose of acceptance criteria.
- The purpose of decomposing epics into stories and why this has to be done.
- Iterative design
- Business Value as a Driver of Prioritization
- Examples and benefits of iterative design
- The point of MVP in iterative design
- The agile view of releasing software
- Moving from waterfall to agile
- Things to keep in mind if you are introducing agile to your organization
- Places to look for more resources to tune your own implementation of agile
Unique Value of Course:
Agile 101 presents a unique and balanced combination of theoretical and practical information. It provides actionable insight into making the transition from waterfall to agile and an appreciation of the various roles in Agile that are needed for success. It provides participants with an overview of iterative design and a detailed view of the Sprint cycle. Students will also gain insight into the issues to be overcome and the potential benefits of agile.
- Understand the Agile Manifesto and be able to explain the change-driven software development point of view.
- Understand and be able to explain the benefits that an agile implementation brings.
- Understand the roles, responsibilities & differences between the three core roles of the agile view (product owner, scrum master, developer).
- Understand the typical agile development cycle (“sprint”) as well as the supporting activities for continuous improvement and feedback.
- Understand core agile concepts including Minimum Viable Product (MVP) and iterative design, and the benefits that these provide.
- Understand the value of good user stories, the difference between stories & epics, and the components of a story including acceptance criteria.
Who Should Attend:
- Business Leaders
- Business Analysts
- Business Process Analysts
- Business Process Managers
- Project Managers
- Business Architects
Line of business managers and supervisors