Agile roles

By Anonymous
There are a number of different roles in the agile methodology, and these need to be well-understood to make agile work effectively in your organisation. In particular, the scrum master and product owner need to have enough time to devote to doing their roles properly.


I must mention that as a female developer, I find a lot of the terminology used in Scrum rather macho and off-putting. I would like to see a shift in the culture on this, but unfortunately, the terms seem to be pretty ubiquitous these days.

A Scrum team. Photo by Nghungdo –  CC-BY-SA 4.0.

Developer

The agile developer is a team player who commits to standardised development practices and sharing knowledge across the team. They are comfortable in different layers of the stack,m though they generally specialise in one of the layers.

In agile methodologies, the development team gets to decide which of the top priority stories in the product backlog they will work with next.

Scrum master

The scrum master manages the scrum process. He or she convenes meetings, protects the team from other tasks, removes impediments, problem-solves, manages the scrum board and the burndown chart, and works with the product owner on prioritising the user stories in the product backlog.

Product owner

The product owner is responsible for liaison between the development team and the stakeholders (both internal and external). He or she "grooms" the backlog, prioritising user stories, adding new ones, liaising with customers and other stakeholders to find out what they want.
Part of the product owner responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the scrum team. This is key to successfully starting any agile software development project. The agile product owner does this in part through the product backlog, which is a prioritized features list for the product.

Pigs and chickens

The developers, as people who are committed to the project, count as "pigs", whereas managers, who are only involved, count as "chickens". This is based on the fable of the chicken and the pig. This story has now been removed from the official Scrum process.

Comments

Post a Comment

Popular posts from this blog

We're in Onstream

By Anonymous
The pilot phase of the Brookes ID project was announced in the latest issue of Onstream , the staff magazine of Oxford Brookes University: Brookes ID (Individual Development) is an inclusive co-curricular framework which has been created with students and is a PESE (Programme to enhance the Student Experience) project. It recognises and rewards student engagement and commitment beyond their programme of study and is aligned to the Brookes Guiding Principles. As part of the Brookes ID initiative a new app has been launched which will run this semester as a pilot, leading up to the official launch of Brookes ID expected in September 2017. The Brookes ID app has been developed by the project team (Professor Alison Honour ADSE, Dr Bob Champion PLSE, Lindsay Williams PLSE, Yvonne Aburrow) and the Student Experience team in OBIS, in partnership with students. It monitors the extra and co-curricular activities of students and rewards them with ‘achievements’. Initially the number of activiti
Read more

Agile methodology in the wild

By Anonymous
Image
Agile methodologies like Scrum sound amazingly efficient when presented by people who have implemented them in a non-hostile environment. But conditions are not always perfect, and things can sometimes go wrong. One of the key features of agile project methodologies is that they have different types of meetings . Each different type of meeting has a very specific function. They can become tedious and unproductive if they deviate from the prescribed form and function. With that in mind, let's look at the different types of meeting, how they are meant to work, and what can go wrong. Three Amigos     © Copyright  Peter Trimming  and licensed for  reuse  under this  Creative Commons Licence . Three Amigos This is a relatively new type of meeting in the agile toolkit, and was developed in 2013 . Essentially, this is a meeting during which the business analyst (BA) presents the requirements and tests for a new feature. The Three Amigos (BA, developer, and QA) discuss the new feature and
Read more