From the course: Agile at Work: Planning with Agile User Stories

What you should know

- As we embark on this deep dive into user stories, let me provide a little broader context. When we look at the team level, there are three things that are systemic to agile ways of working. You need to have a cross-functional team, so I mean, you need to have the people with the skills and experience to do this stuff in small time increments, you need to be able to decompose your requirements down to create actionable user stories, and you need to be able to do an adequate amount of planning to be able to get those stories done. There are many elements that we need to see to really get the benefit of agile ways of working, like frequent feedback between team members and between the team and their product owner. But, for this course, we'll focus on taking feature-level requirements, sometimes called business capabilities or epics. These how our high-level requirements will decompose into user stories, which will then be prioritized in a product backlog.

Contents