Agile Scrum Project Roles
A 59 Seconds Agile Training Video
Continue to Part 3 Below
Introduction to the Scrum Project Roles
A 59 Seconds Agile Article
This article provides an ‘Introduction into the Scrum Project Roles’ and looks to discuss the different roles that are involved in an Agile Scrum Project.
Why do traditional projects fail?
One of the leading causes of traditional software development challenges and failure, is the lack of involvement of stakeholders and user groups in the development process. Customers see progress as tangible working product functionality.
According to Murray and Crandall, a lack of user involvement occurred in 29% of failing projects, while ineffective stakeholder management occurred in 51% of failing projects.
“Have you experienced that the plan changes every meeting”?
This is another cause of failure, ‘over planning’. When targets moved and the schedule frequently changes, it causes confusion among team members. Another factor that causes project failure is ‘insufficient communication’.
Communication becomes insufficient when we take it for granted. Are weekly meetings enough when discussing challenges and clarifying scope or targets? Lacking visibility and direction, especially when there are changes to the plan, will cause the team members to fail to see the big picture. The other question would be who is involved in those meetings? Are there consultations with stakeholders or customers on a constant basis?
Think about how the communication flows in your project team. Remember an incident when you bought something online and what you received was different. What comes to mind when you received the product? How did you react? This is another cause of traditional project failure, ‘all at once delivery’.
One characteristic of a traditional project is it is controlled, and not open for change. Once the requirements are locked in and the scope is define, the customer will expect that the product that will be delivered, is based on what was communicated as requirements. They will need to wait to see the results, which can lead to frustration.
Agile Scrum Project Roles
A 59 Seconds Agile Video Animation
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.
The Agile Scrum Roles
A 59 Seconds Agile Infographic
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum: