Software projects start with functionality and requirements. The clarity and quality of the requirements drive the deliverables of the project and set the expectations of customers. Managing requirements can be a challenge because we have been taught to capture all requirements up front, and achieve customer sign off. This process does not allow for change, and all software projects have change.
Enter user stories. Authoring project requirements as user stories is one of the most common approaches across any agile method. In this course, you will learn what a user story is, how to build and author them and how to manage and communicate them to users. The course format consists of multiple lecture topics, group exercises and group discussion. Ample time will be devoted to analysis of the “real-world” industry experiences of the instructor based on case study examples and experiences managing agile projects and coaching agile project teams.
Course Outline
- Past Approaches to Requirements - Explore more traditional approaches like the V Model, “capturing” all requirements up front and the hurdles with trying to get it 100% correct in the beginning.
- Alternatives to Traditional Approaches - We will explore use cases, scenarios and user stories. Each has its own benefits and detriments - we will explore each one in detail.
- The Product Backlog - The Product Backlog is the key to any successful Scrum team. We will explore what comprises a good Product Backlog, techniques for managing it and what happens when it goes unattended.
- The Product Owner - The key role in tying everything together, we will look at what makes a good Product Owner, the responsibilities and how to involve customers.
- User Roles - Understanding who uses our system is key. We will look at what a user role is and how to determine then for your projects.
- User Stories - Knowing a good story from a bad story can make a project succeed or fail. We will look at how to gather stories, what makes a good story and how to build the end to end vision of the project.
- Prioritizing Stories - Not all stories are equal. Knowing what to work on first can be an art form. We will look at financial techniques like NPV and IRR and techniques based on desirability, specifically the Kano method.
This hands-on, one day course is valuable to all participants of software projects including analysts, project managers, developers, testers and more.