This article looks to discuss ‘Agile User Stories and Tasks’. It provides an introduction to the Agile User Story and how to create them, along with the role of Agile Tasks.
Agile User Stories and Tasks
A 59 Seconds Agile Training Video
Continue to Part 2 Below
Agile User Stories and Tasks
A 59 Seconds Agile Article
This article provides an ‘Introduction to the Agile User Stories and Tasks’ and looks to discuss what a user story is and what a Task is.
User Stories and Tasks
It isn’t enough to just have a well-built to-do list for your team, tasks also need to be estimated, and the process needs to be communicated. Think back to the example we discussed earlier. You were working on a project where you ran into obstacles, lack of communication, and a lack of planning at every turn. This led to team frustration and a struggle to accomplish the development you needed to complete.
When your team is beginning a new project, you can start on the creation of value by clarifying the project vision, the initial release plan, and the selection of project resources. Once this is done, you’ll be able to take the requirements and features of the product you’re developing and develop the information into epics. This represents the move from the initiate phase into the plan and estimate phase.
These epics are wide-reaching stories that explain general requirements for the product and form the basis for the user stories you’ll develop later. Think of these epics as books and the user stories as paragraphs or chapters. The epics go into the product backlog, which also contains the user stories and anything else that describes the requirements for the product.
Continue Reading —> Next
The Agile User Stories and Tasks
A 59 Seconds Agile Video Animation
Continue Reading —> Next
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
Continue Reading —> Next
The Agile Frameworks
A 59 Seconds Agile Infographic
Continue Reading —> Next
Agile Scrum Master Training Course
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum:
Continue Reading —> Next
