Course Overview
Many businesses are realizing that requirements are just as important in agile & Scrum projects as they were in previous projects. While many development teams are having success with agile & Scrum, dealing with requirements still has challenges because of Scrum’s different philosophy on requirements, where the details evolve and emerge as the project proceeds.
Getting a shared vision of the product to be developed right remains a significant impediment, and involving the right people outside of development remains a key driver for product acceptance. It’s the same problem as ever but needs doing in a different, agile way.
In this class Geoff Hewson describes many tested methods that can help any organization using Scrum improve the way it handles requirements. The key differences and challenges of requirements in agile/Scrum projects are identified and participants will learn new agile requirements techniques as well as learning how to leverage what you already know about requirements within the agile approach. Read
More.
Who Should
Attend
This is an intermediate level seminar that is intended for product owners, business analysts, product managers, and business representatives who are tasked with the providing requirements for agile software development projects.
Project Managers, Scrum Masters, Team Leads and Managers responsible for facilitating and managing agile projects will gain value by understanding the essential work involved in developing agile requirements which will better equip them to lead their teams.
Benefits and Learning
Objectives
This 2-day workshop combines instructor-led discussion with practice sessions and multiple group exercises, and emphasizes several sensible practical techniques that can be immediately applied on any project to improve requirements development and management in your organization.:
- The big picture on agile requirements – dealing with common misconceptions
- New requirements roles in Scrum - The Product Owner – Who will do it? How will we make it work?
- Scrum’s new way of capturing & organizing requirements – the product backlog - How to do it right.
- Changing how requirements are developed to feed an agile/Scrum project comprised of many short duration sprints.
- Multiple techniques to identify requirements for the Product Backlog – user stories, story mapping, use case analysis, feature decomposition etc.
- Overcoming the misconception “you don’t know what will be in the final product” – by using release plans, epics and marquee features effectively.
- Harness the strength of the agile & Scrum approach - where the customer doesn’t know what they want, letting the ‘right’ requirements emerge as the project proceeds, coping with changes in project direction.
- Planning & Working “Just in-time” – always having just-enough requirements done so unnecessary work is minimized – but how do you do it?
- Working collaboratively with the team to determine the right implementation order for requirements – not breaking the sprint
- Planning requirements for testing – requirements still have to be testable on agile projects.
- Balancing focus on immediate needs with “big picture” concerns - fitting in Architecture and non-functional requirements.
- Staying involved with the development team – making sure sprints deliver useful, working software based on requirements.
- Read
the Full Course Outline
Plus, receive valuable takeaways. The workshop
manual helps you explore the guiding concepts and principles,
tools and techniques specific to agile requirements along
with valuable concept explanations and facilitation techniques
used within the course.
Read the Instructor Bio: Geoff
Hewson.
Other courses led by this instructor:
January 24-25 Vancouver, BC $1095
CAD Register
May 15-16 Vancouver, BC $1095
CAD Register
Read information
on payment,
cancellation policy and course locations.
