Early registration automatically gets you $ off of the normal registration price! Early registration discounts end in advance of the first training day.
Dates & Locations
|No open enrollments at this time, please check back.|
The application of Agile principles and practices on software development projects enables a project team to quickly develop working software that meets business needs. In Scrum, teams work in 2-4 week Sprints to produce production-quality software driven by business priorities using an empirical, adaptive approach. This course provides an in-depth understanding of how Agile and Scrum teams deliver business value.
You will learn to apply the basic practices of an Agile approach, with a focus on Scrum. You will apply what you learn in a series of exercises that take you through the identification of user stories, project/release planning, Sprint Planning, and Sprint Execution. Participants will build and manage a Product Backlog, a Sprint Backlog, and a Release Plan.
- Apply Key Concepts and Terms of Agile and Scrum to Project Situations
- Explain the Methodology’s Benefits and Key Techniques
- Experience the Progression of Key Activities and Artifacts
- Gain a Deep Understanding of Different Practices and When to Apply Them
- Help Others Understand and Apply the Practices and Principles
- Agile/Scrum Fundamentals
- What are agile practices and principles?
- What is “iterative and incremental” development?
- What is Scrum?
- Scrum Roles and responsibilities
- What is a User Story?
- How to identify and write good User Stories
- Non-functional requirements
- Evolution of requirements during a project
- Estimation and Prioritization
- What is a Product Backlog?
- Creating the initial Product Backlog
- Agile Estimation Overview
- Different ways to do Agile estimation
- Prioritization- who, what, why, and when?
- Definition of ”Done”
- Release Planning
- What is Release planning?
- How is an Agile release plan different from a traditional release plan?
- Methods for creating a release plan on an Agile project.
- Planning a Sprint
- What is a Sprint Backlog?
- Conducting Sprint Planning Meeting Part 1 & 2
- Developing the Sprint backlog
- Sprint tasking and estimation
- Running a Sprint
- Evolution of requirements during a Sprint
- Conducting the daily Scrum
- Managing the Sprint scope
- Tracking progress; recognizing problems
- Closing a Sprint
- Conducting a Sprint review
- Conducting a Sprint retrospective
- Reporting project status
- Updating the backlog; Backlog grooming
- Closing the Sprint
- Managing the Product Backlog and
- How does the Product Backlog change during a project?
- How do you control changes?
- How does the Release Plan change during a project?
- Agile Software Engineering
- Application of typical Agile Software Engineering practices such as Continuous Integration, Test Driven Development, and Pair Programming
- Agile Testing
- Testing during the Sprint
- Agile testing practices
- Roles/responsibilities in testing:
- Team Testers
- Product Owner
- Independent Test Group
- Anyone who will actively participate in a project using this approach
- People on the edges of the project (secondary customers, management staff, and participants in related processes)
- Project teams are encouraged to attend as a group
- Basic understanding of Scrum
- ICON's training course, "Scrum Overview"