At a glance
2 days
AUD $1650 inc GST
NZD $1750 + GST
including in-house delivery.
Agile Initiate Phase Start Me Up
This course dives deep into the initiation phase of the Agile process and gives participants a thorough understanding and hands-on experience of the steps and techniques involved.
The initiation phase relies on the successful identification and prioritisation of user stories. User stories are the core of Agile requirements, capturing features of the application in small (1-3 day) testable chunks that deliver business value. Not all stories will require developing software, but many of them will, so stories are also the interface between the business, the developers, and the test analysts.
This course takes you through the process and the deliverables involved in the initiation phase of an Agile project. You will take a case study through each of the initiation steps - solution refinement; story identification; story prioritisation; story estimation; and release planning - looking at the deliverables from each step and the techniques used to produce them.
This course is part of the Agile Academy curriculum.Software Education is proud to be a founding partner of the Agile Academy.
Intended For
Analysts, developers, testers, project managers, architects and subject matter experts. Team leaders & line managers can also get a good overview of the process and practices to use in non-software development environments.
Prerequisites
Some understanding of Agile practices would be beneficial. For an introduction to Agile practices see our Taste of Agile course.
Learning Outcomes
Participants will gain an understanding of the content and structure of the initiation phase of an Agile project, and will gain experience in the various practices that make these activities successful.
Content
Context
- Background
- Agile values and principles
- A simulation of the Agile development process
- Introduction to common agile practices
Objectives and structure of the initiate phase
- The initiate phase in the overall process
- Who, why, how, what and for how long?
- why - because we want working software
- how - steps of the deliver phase
- what - creation of standard artefacts for external parties
- who - roles and responsibilities
Concept review
- What happened in concept? Why?
- Common techniques used in the concept phase
- What should have been produced?
- What to do if the concept phase wasn't completed
Preparation and kick-off
- Preparation
- Individuals review outcomes of the concept phase
- Identifying the stakeholders
- Understanding the current situation
- Planning and resource for the initiate phase
- Techniques
- Workshop approach and the workshop daily cycle
- Facilitation techniques and tools
- Daily stand-ups, retrospectives, story wall
- Kick -Off
- Group review outcomes of the concept phase
Refine solution
- Purpose and deliverables
- Challenging assumptions and brainstorming for cost-effective alternatives
- Reviewing and refining project risks
- Refining the quality and success criteria
- Establishing a technical vision and solution architecture
- Investigating technical risks with spikes
- Using prototypes (lo-fi, paper and hi-fi) to solicit quick feedback
Story identification
- Purpose and deliverables
- Introduction to stories
- INVEST characteristics of a good story
- Independent, negotiable, valuable, estimable, small, testable
Method Used
Lecturing is kept to the minimum necessary, most of the learning is achieved through applying the practices and techniques in group exercises and a case study.
