Attendees will identify and document epics, user stories or features and build an understanding of the challenges faced in matching business priorities with technical capabilities.
Attendees will understand how to form and manage a product backlog by working with technical and business stakeholders. They will see how business value is delivered through a series of sprints. The focus of the training is on taking an organisational view to delivering value through the development and enhancement of IT solutions.
The course is run in the style of an agile project during which the delegates will attend daily stand-ups, produce a product vision and user stories, perform poker planning and engage with other stakeholders. A simple case study is used throughout the course enabling attendees to experience the lifecycle of an agile project.
Course delegates will learn how to develop a product backlog starting with epics and transforming these into user stories.
On-site clients may choose to tailor the content to suit their own requirements for example, by adding contrasts with more formal approaches that may also be applied in some projects,
The training is broken down as follows:
Section 1 Agile development – the role of the product owner and business analyst
The first section of the course introduces the roles of product owner and business analyst and positions their place within an agile project. The following specific topics are covered:
- Agile project roles – scrum master, business analyst, product owner, project sponsor, end-user, developer, tester, UX designer
- The Agile Manifesto
- Agile principles
- Agile methods – An overview of Scrum and XP to assist attendees in understanding how development work is likely to be taking place.
- Comparison of agile with other project lifecycles
Section 2 Starting an agile project
The second section of the course starts to explore the principles of agile in more depth. In particular, it attempts to create an agile mindset, introduces important terminology and techniques used, and starts to produce agile deliverables. The following specific topics are covered:
- Introducing the daily scrum
- Understanding the project vision and objectives
- Creating User Roles and Personas
- Identifying product features
- Writing user stories
- Creating the product backlog
- Estimating features using planning poker
- Prioritising features – based on business value, functional and architectural risk
- Estimating the project size
- Defining the release and sprint schedule
- Drawing a burn-up chart
- Software tools (e.g. JIRA) that support agile development
Section 3 Moving through the sprints
The third section of the course starts to develop of a view of the activities once sprints get underway and functionality starts to be delivered. It looks at the activities that take place at the end of a sprint. The following specific topics are covered:
- Getting the development team started on something
- Product Owner and Business Analyst activity during sprints
- Options engineering
- Feature splitting (splitting epics into stories)
- Technical debt
- Architectural spikes
- Writing acceptance criteria and tests
- Sprint retrospectives
- Supporting business implementation – hints and tips to ensure that business value is maximised