Scrum Master

User stories are more important than epics and themes

Submitted by Barnaby Golden on Wed, 30/01/2019 - 17:18

Waterfall

Scrum teams take user stories into sprints.

For many teams that is the end of the conversation. They do not need anything else to describe the work they are doing and the requirements they plan to do in the future.

For other teams, particularly those with a long product backlog, it may be beneficial to use other terms for requirements. Terms like 'epic' and 'theme'.

Products versus Projects

Submitted by Barnaby Golden on Mon, 18/04/2016 - 15:58

 

Agile favours a product approach over a project approach

Software development has traditionally been done in projects.

Wikipedia describes a project like this:

In contemporary business and science, a project is an individual or collaborative enterprise, possibly involving research or design, that is carefully planned, usually by a project team, to achieve a particular aim.

Scrum myths

Submitted by Barnaby Golden on Fri, 27/02/2015 - 11:33

 

The following are some common Scrum myths.

 

Velocity is a measure of performance

Isn't a higher velocity a sign of a more productive team?

The Scrum guide is very clear that velocity is purely about establishing the likely capacity of a team for future sprints. The actual value is irrelevant, it is the predictability that is important.

 

8 golden rules of a development team

Submitted by Barnaby Golden on Wed, 07/01/2015 - 16:24

Golden rules of a development team, compiled from personal experience and from a number of books, academic papers and other sources.

1. Use the same deployment mechanism for all environments

When you do something often, you get good at it. So deploy to all environments using the same mechanism. That way, when you deploy to production things less likely to go wrong.

 

Sustainable Pace

Submitted by Barnaby Golden on Sat, 12/07/2014 - 10:29

It has long been a tradition in waterfall style projects to associate long hours with increased productivity. A recurring pattern is up-front planning, followed by realisation that a deadline is not going to be achieved and then finally a push to increase working hours.

What are Story Points?

Submitted by Barnaby Golden on Sun, 30/12/2012 - 11:03

Nothing else in Scrum generates more confusion than story points. So what are they and just as importantly, what are they not? Here is my definition:

Story points represent the relative difficulty in completing development tasks that produce business value

© Copyright 2018 bhgagile Limited

Paperblog

Software Development Blogs - BlogCatalog Blog Directory