Search

Agile Filter

How Not To Be Agile -An Effective Product Backlog

IntroductionHello and welcome to this, the third article in the series ‘How Not to be Agile’.‘How Not to be Agile’ may seem a strange title for blogs about how good Agile is!  What I intend to do over this series of articles is to share with you the misinterpretations, omissions, and mistakes that people make that significantly reduce the potential benefits when an organisation, or a part of it, embark on an Agile Transformation.Last time, I discussed the potential pitfalls of not having a suitable Business Case for whatever it is that we are trying to achieve, be it a new product, a major change to an existing product or the Agile transition itself.This time, I will cover some of the misunderstandings and malpractices that I have come across with respect to the next major item to consider in any Agile framework, the requirements.  The most often used term for the requirements list is the Product Backlog from Scrum; I will use this and other Scrum terminology in this article but you can use whatever names you like; it is the content and management of the requirements list that is important.I will start with a description of the Product Backlog process and then give examples of what has and could go wrong if not follows the Product Backlog tips.The Definition of Scrum Product Backlog Having achieved an agreed Vision and Objectives and decided that the Business Case for the product development is viable, the business stakeholders and development team need to discover a list of ‘business requirements’, at the same level of detail, so that the development team can develop the product in a series of short development timeboxes.These ‘requirements’ become Product Backlog Items (PBI). What is a ‘Requirement’?Functional Requirements:There are 3 commonly used ‘structures’ used to express ‘Agile functional requirements’:Elementary Business Processes (EBP) – the names of EBP, usually extracted from the results of the Business Process Modelling exercise concerned with the area of the business that the product is for; for example:                                                                                              ‘Capture Customer Details’Use Cases – from the Unified Modelling Language (UML).  Only the names of the Use Cases, again, usually extracted from the results of Business Process Modelling exercise and the example is the same as for the EBP aboveUser Stories – a technique from eXtreme Programming which states the user of a business process, the name of the process and why the  process is needed; for example:                                                                                                    ‘As a sales person                                                                                  I need to Capture the Customer Details                                                                                        So that payment can be taken’For all the 3 ‘requirements’ types, it is only the names of the business process that are needed (with the addition of the other 2 clauses in User Stories); there should be no lower level details in the PBI.The level of detail for all of the above can be summarised as:                                            ‘The name of one job, being performed by one person, at one time’Non-Functional ‘Requirements’:In addition to the Functional Requirements, the ‘What’, the business will also express the needs of ‘How’ the product will perform such as:All screens must refresh within 5 secondsThe system must be available 24/7/365The system must conform to the company marketing graphic languageand so on and so forth.These Non-Functional ‘requirements’ can be added to the Product Backlog in a separate section from the Functional Requirements or in a separate ‘document’.What A PBI Is NotThere was a fashion, that still exists in some places, to have ‘Technical User Stories’; ‘User Stories’ those name technical activities that need to be done; for example:As a database designer                                                                         I need to create data access scripts                                                     So that the product can store and retrieve the data that it needs to useSuch User Stories would just be stating elements of a team member’s work and do not add anything to the understanding of the business needs which the Product Backlog is meant to represent.It is my strong recommendation that so-called ‘Technical User Stories’ are NOT used because the Product Backlog becomes large, unwieldy, almost impossible to order by business value and prioritisation; the estimated effort for these technical needs are included in the estimation of the ‘business’ PBI; more of which later.It is true that there may be a need for some activities to set-up the technical environment before the development team can start developing the product, some of which are out of the control of the development team; these activities should take place in parallel with creating the initial Product Backlog.Creating a Product BacklogOrdering the Product BacklogThe whole point of Agile is to deliver a product incrementally so that the business can accrue the best value in the shortest possible time.It, therefore, follows that the product needs to be developed by developing the PBI in the business value order; the highest business value PBI first.Therefore, the PBI needs to be ordered by business value. I will not go into the techniques for ordering PBI, they are well documented elsewhere but I will give an example, later, of what happened when one team did not use Product Backlog ordering.Estimating the PBIWe create the initial Product Backlog just after agreeing on the Vision and Objectives and ensuring development viability via the Business CASE  but before development begins; it needs to be estimated in some way to determine how long it may take to develop the product and consequently how much it may cost to develop.It is a tenet of all Agile frameworks that only the development team is allowed to estimate the PBI.  Once done, these estimates will ‘inform’ the Business Case and analysis can be made to see if the original ‘high-level’ estimates in the initial Business Case are of the same order; a decision can be made as to whether the development is still viable.Types of PBI estimatingThere are 2 generally used types of PBI estimating:1. Absolute Estimating:  Whereby each PBI is estimated by how much time it would take go from just its name to ‘potentially shippable’ functionality.  Of course, the tasks include analysis, design, construction and testing and what normally happens is that each ‘skill’ will estimate the time it would take for their part in the process and the times summed to get the overall estimate.2. Relative Estimating:  Whereby the team chooses the PBI which is likely to be ‘the smallest’.“The smallest in what respect?”  you ask.  The ‘smallest’ does not directly consider time; the PBI criteria that are considered are size and complexity.However, opinions of size and complexity will vary amongst all team members depending on their skill and experience; what may seem ‘simple’ to an experienced developer may seem complex to the less experienced person.  Similarly, although the analysis and construction may seem simple, the testing may be complex.For these reasons, it is highly recommended that Relative Estimating is done using ‘Planning Poker’ which is well described elsewhere (see ‘Planning Poker: An Agile Estimating and Planning Technique’); suffice to say here, that once the team have decided which is the ‘smallest’ PBI, they give it a ‘Story Point’ of 1 and all other PBI are estimated with respect to their individual relative size and complexity compared to the ‘smallest’.So which estimating technique to use?1. Absolute Estimating can take a long time; it is akin to the traditional way of estimating for the Project Plan.  Also, it has been established that, generally, we are not very good at estimating in time; the larger the thing we are trying to estimate, the worse our estimates get.  However, the technique is familiar to most people and does not require a change of mindset to produce estimates.2. Relative Estimating requires a totally different mindset amongst the development team members because, initially, not only are they using unfamiliar criteria to estimate the PBI but also, they are estimating in collaboration with other team members with different skill sets and experience.Despite there being ample evidence that Relative Estimating takes less time overall and allows the stakeholders and development team to focus on business benefit being delivered, because of the ‘difficulties’ of introducing Relative Estimating, many teams revert to time estimation and tracking time.  Also, as we will see in one of the Case Studies below, an organisation’s choice of requirements management tool can make the use of Relative Estimating seem a waste of time for team members.Another Potential Problem with Relative EstimatingSo, having carried out ‘Planning Poker’, the development team now know the total number of ‘Story Points’ that the development represents; not much good to the business stakeholders who want to know how long it is going to take and how much it is going to cost.On completion of the initial Product Backlog and before development begins, we need to ‘translate’ this total ‘Story Points’ into time.An Agile Team’s progress is measured by the number of ‘Story Points’ that they deliver in one Sprint; known as the team’s ‘Velocity’.So we need a knowledge of the team’s Velocity in order to establish an estimate of how long the development is likely to take; for example, if the total number of ‘Story Points’ is 200 and the team’s velocity for a 2-week Sprints is 10, then the estimated time to complete all the PBI is:         200 ‘Story Points’ / 10 ‘Story Points per Sprint  x 2 (the number of weeks per Sprint) = 40 weeksHowever, at the start of an Agile transition, we do not know what the team’s Velocity is or will be.  There are 2 methods to determine what the Velocity may be:1. The team takes one of the ‘smallest’ PBI (with a Story Point of 1) and does a traditional break down to the tasks involved and estimate those tasks in time;  1 ‘Story Point’ is equivalent to the time represented by the sum of the times estimated for all the tasksThe team’s Velocity may be estimated by:                                      ‘The number of working days in the Sprint / the estimated days for 1 Story Point’For example, if the ‘time estimate’ for a PBI of 1 ‘Story Point’  is 1 day:                                             10 working days in 2-week Sprint / 1 day = Velocity of 10This velocity can then be used in the formula above to determine the estimate for the potential total time for the development.2. The development team is allowed to start development for 2 or 3 Sprints taking PBI from the top of the Product Backlog.  At the end of the ‘experiment’ period, the total number of ‘Story Points’ for the completed PBI divided by the number of Sprints completed becomes the Velocity to use in the formula above to determine the estimate for the potential total time for the development.The potential problem with this method is that management have to release funds for this experimental period without knowing the values to feed into the Business Case to determine whether the product development is viable before development begins.Once teams have completed 1 product development, we recommend that the team members are kept together for other product developments even though the business area or technology may be different.  Having a team that works well together is more important than creating teams in an ad-hoc manner.  A team’s Velocity varies insignificantly over different product developments and so can be used directly in the formula above to determine the estimate for the potential total time for the development.\Scoping the Product BacklogGenerally, Agile product developments have strict deadlines so that the major benefits can be accrued; benefits such as competitive advantage, meeting marketing needs, meeting customer expectations or complying with regulations.Also, Agile teams comprise all the skills necessary to take the PBI from ‘names’ to a potentially shippable product; not all team members are full-time but the team is fixed.Therefore, generally, the costs for a fixed time product development are also fixed.Given the classic ‘Iron Triangle’ of development variables:If we fix time and cost, then the only thing that can vary is the Requirements that are delivered in the fixed time for the fixed cost.It is quite probable that the initial Product Backlog will contain more PBI than could reasonably be developed in the fixed time available; because the stakeholders/Product Owner has ordered the Backlog by business value, it is relatively straightforward to ‘draw a line’ underneath the lowest PBI in the list that will probably be developed.  We do not remove the lower value PBI because it has been often found during development that a high-value PBI is actually dependant on one of the lower value ones and the ordering has to be amended.Stakeholders need to understand that even though some requirements (PBI) have been requested, it is probable that they will not be delivered.But the Product Backlog scoping does not stop there.  The ‘story Points’ for the PBI are estimates and, by definition, they are not accurate.  In the past, to account for ‘inaccurate’ estimates, organisations have added contingency in time and costs to the estimates.However, in Agile environments where the time and costs are effectively fixed, the development needs some ‘wriggle room’ for when estimates are proved significantly wrong and when requirements change during the development. For an effective Product Backlog, you need to follow Scrum Product Backlog tips.The Minimum Viable Product (MVP)The development team must agree with the Product Owner/Stakeholders which PBI represent the Minimum Viable Product, ie what is the minimum to be delivered in the fixed time in order to accrue the minimum benefit required.There are ‘rules’ how big this MVP can be.  It has been found, from hard-won experience that for a ‘comfortable’ working environment:1. When a team first starts an Agile transformation they should accept PBI in the MVP which represent around 50% to 55% of the estimated effort; ie if there are 200 ‘Story Points’ in the probable PBI, then the MVP should only contain the highest value PBI whose ‘Story Points add up to between 100 and 110.2.When the team and the organisation are reasonably Agile-mature, between 9 months and a year of transformation, the team can accept PBI representing up to 65% of the total estimated effort in the MVP.3.When the team and organisation are fully Agile-mature, PBI representing up to 70% by estimated effort may be accepted in the MVP.  It has been found that no matter how good the teams and organisation are, the variables that come along with all product development make promising more than 70% by estimated effort fraught with problems; the teams must strive not to give stakeholders over-expectations.  The MoSCoW RulesSome Agile Frameworks recommend using a technique called MoSCoW to ‘categorise’ the PBI.  The acronym stands for:Must Haves: Those PBI that is essential to the product; equivalent to the MVP above.Should Haves: Those PBI that is important but there is a workaround for them if they not completed in the fixed timeCould Haves: Those PBI that might be developed if all the Musts and Shoulds have been completed before the end of the fixed timeWon’t Haves:  Those PBI that was initially discovered but was not likely to be completed based on the estimates for the more valuable PBI“The ‘o’s are just for fun”!Using the MoSCoW rules allows the Business Case to be prepared with 3 scenarios:The ‘Best Case’ scenario where all the probable PBI are completed; giving the best benefit in the fixed timeThe ‘Expected Case’ scenario where all the Musts and Shoulds are completed giving the majority of the expected benefits in the fixed timeThe ‘Worst Case’ scenario where only the Musts are delivered giving only the essential expected benefits in the fixed time.Case Study 1:I was working as a business analyst and ‘just-in-time’ Agile trainer/coach for an outsourced team building a replacement system.  The team had 6 full-time business representatives to specify the Agile Requirements (UML Use Cases in this instance).Creation of the Product Backlog went smoothly; a good ‘To-Be’ Business Process Model was created and Use Cases to be included in the new system were identified; there were 92.Unfortunately, I was due to go on 3 weeks holiday, so I briefed the team on how to order the Product Backlog and we ran through some Planning Poker with a few of the Use Cases.When I came back from holiday, I discovered that the team business representatives had had problems in ordering the Product Backlog and had abandoned the attempt because they considered that all the PBI were essential.  Also, the whole team had had problems with Planning Poker because they didn’t know enough about the low-level details.It had been decided to prototype all the Use Cases before estimation and the developers were split into 3 sub-teams for prototyping and the business representatives split into 3 pairs.I had taught the team that the prototyping of any PBI should only go through 3 cycles:1. Investigation where a very rough ‘first draft’ is specified, built and reviewed to make sure that the developers are ‘on the right lines’2.Refinement where the majority of the functionality is specified, built and reviewed3.Consolidation where any ‘tidying-up’ was specified, completed and the complete prototype demonstrated to the wider stakeholder communityIf it takes more than the 3 cycles, then something is wrong with the detailed process being followed.The time taken to produce a prototype should be no more than 2 days but it can be as short as 2 to 3 hours if done in a workshop.Unfortunately, it was decided to pick Use Cases to prototype based on their perceived ‘easiness’ and ‘rotate’ the business representative pairs around the prototype builders such that one pair specified the Investigation, another pair reviewed the Investigation and specified the Refinement and the third pair reviewed the Refinement and specified the Consolidation. At the ‘final’ review, with all 6 business representatives present, the ‘final’ prototypes were significantly different from what was originally specified for the Investigation and ‘recriminations’ took place.  So the prototype developers started again.It had taken 3 weeks to develop the prototypes for 6 PBI!I asked the project manager what his estimate was for completing the prototypes for all the PBI; he calculated that the time that would be necessary was 1 month longer than the specified length of the project.Suffice to say that I worked with the customer representatives to convince them that it would be improbable to complete all the PBI in the fixed time/fixed cost development contract and helped them order the Product Backlog and decide on an MVP. It is worth noting this product development had a Vision, there were no stated objectives nor a visible Business Case.I worked with the developers and business representatives (who were full team members) to ‘play’ Planning Poker.Actual development work started one week later; PBI were completed in the fixed time that equated to approximately 70% of the expected business benefit; a further short project was commissioned to bring the expected business benefit up to 90%.Lessons:1. Do not go on holiday at a crucial time during the product development lifecycle!2. If the Product Backlog is not ordered by business value, significant time will be wasted prototyping PBI of low business value3. If prototyping is to be used, then the whole team should do it together in a workshop; all views will be accessible to all team members and a consensus reached in the minimal amount of time4. If you are an Agile Project Manager/Scrum Master it is your responsibility to keep the team ‘on track’ and to question decisions that may cause a risk to the projectCase Study 2:I had been asked to do some Agile coaching for some teams in a global organisation that was undertaking the Agile transformation of one of their divisions to use SAFe®/Scrum; the transformation had been running for 6 months.  There were 4 teams distributed around the globe doing support work to enable 24-hour coverage for this global organisation.The reasons for SAFe®/Scrum for this transition I covered in my first article.When I arrived Product Backlog requests were arriving daily to the team members from systems users and the individual team member decided whether the requests were important enough to interrupt the work that they were already doing; the Product Owners were not involved in the decision-making process at all.  As a consequence, there were many requests that had been started and abandoned in favour of ‘questionable’ higher priorities and I discovered that some requests had been sent to inappropriate team members, the work would have been better carried out by members of the other global teams.Furthermore, although the teams were doing some Relative Estimating at Sprint Planning (not before), they were focusing on time estimates because that was what the requirements management tool required and what management was tracking progress by.  I shall cover the pitfalls of Sprint Planning in my next article.I started resolving the Product Backlog issues by speaking to all the Product Owners, mostly via video-conferencing, to see if they understood the problems that the current Product Backlog processes were causing.  They did have some understanding but explained that that was the way they worked before the Agile transition and believed that changes to the process were out of their control.I helped them devise a workable process whereby all requests would be sent to  the Product Owners  at a collective address.  They would take turns during a 24-hour period to determine, with Product Managers, the relative priority of new requests against those already on the Backlog.  In addition, once a week, they would ‘get together’ to decide which team would handle any unassigned requests; ‘show-stopper’ requests would be handled as a matter of urgency and handled by whichever team was immediately available and could resolve the issue before their end-of-day.By this process, the Product Owners would gain control of the Product Backlog, there would be less questionable priority decisions and there would be fewer ‘disgruntled’ customers.The process was approved by the Product Managers and all team members apprised of the reasons for the new process and their responsibilities within it.It quickly became obvious at daily Scrums that not all team members were passing all requests that came to them directly from customers to the Product Owners; the process was reiterated to these team members but then the productivity of some of these members decreased significantly.  The cause was that they were still working on their ‘favourite’ customers requests but not reporting it to the rest of the team.The Product Owners then had to analyse the central Change Request system for items that had been completed by their teams but had not appeared on the Product Backlog; the Change Request system was not integrated with the Product Backlogs.Eventually, the ‘lesson’ was learned by ‘miscreant’ team members.Lessons1. Without control of the Product Backlog by the relevant authority (Product Owners), it is impossible to police work to give the best business value to the organisation2. Without control of the Product Backlog, the resolution to some requests may be started and then abandoned in favour of other later requests leaving the customer frustrated3.Estimating by time at the task level wastes a great deal of time; more of which in my next article.ConclusionThe Product Backlog is arguably the most important artifact for product development:The PBI must be ordered by business valueThe PBI must be estimated, preferably by using Planning PokerIts content over time must be controlled by the Product Owner or equivalentTeam members must be closely coached and mentored during the early instigation of process change to ensure their understanding of the need for the change and their compliance

How Not To Be Agile -An Effective Product Backlog

3584
  • by Steve Ash
  • 08th Oct, 2018
  • Last updated on 11th Mar, 2021
How Not To Be Agile -An Effective Product Backlog

Introduction

Hello and welcome to this, the third article in the series ‘How Not to be Agile’.

‘How Not to be Agile’ may seem a strange title for blogs about how good Agile is!  What I intend to do over this series of articles is to share with you the misinterpretations, omissions, and mistakes that people make that significantly reduce the potential benefits when an organisation, or a part of it, embark on an Agile Transformation.

Last time, I discussed the potential pitfalls of not having a suitable Business Case for whatever it is that we are trying to achieve, be it a new product, a major change to an existing product or the Agile transition itself.

This time, I will cover some of the misunderstandings and malpractices that I have come across with respect to the next major item to consider in any Agile framework, the requirements.  The most often used term for the requirements list is the Product Backlog from Scrum; I will use this and other Scrum terminology in this article but you can use whatever names you like; it is the content and management of the requirements list that is important.

I will start with a description of the Product Backlog process and then give examples of what has and could go wrong if not follows the Product Backlog tips.

The Definition of Scrum Product Backlog

Scrum Product

 
Having achieved an agreed Vision and Objectives and decided that the Business Case for the product development is viable, the business stakeholders and development team need to discover a list of ‘business requirements’, at the same level of detail, so that the development team can develop the product in a series of short development timeboxes.

These ‘requirements’ become Product Backlog Items (PBI). 

What is a ‘Requirement’?

Functional Requirements:

There are 3 commonly used ‘structures’ used to express ‘Agile functional requirements’:

Elementary Business Processes (EBP) – the names of EBP, usually extracted from the results of the Business Process Modelling exercise concerned with the area of the business that the product is for; for example:

                                                                                              ‘Capture Customer Details’

Use Cases – from the Unified Modelling Language (UML).  Only the names of the Use Cases, again, usually extracted from the results of Business Process Modelling exercise and the example is the same as for the EBP above
User Stories – a technique from eXtreme Programming which states the user of a business process, the name of the process and why the  process is needed; for example:
                                                                                                    ‘As a sales person
                                                                                  I need to Capture the Customer Details
                                                                                        So that payment can be taken’


For all the 3 ‘requirements’ types, it is only the names of the business process that are needed (with the addition of the other 2 clauses in User Stories); there should be no lower level details in the PBI.
The level of detail for all of the above can be summarised as:

                                            
‘The name of one job, being performed by one person, at one time’

Non-Functional ‘Requirements’:

In addition to the Functional Requirements, the ‘What’, the business will also express the needs of ‘How’ the product will perform such as:

  • All screens must refresh within 5 seconds
  • The system must be available 24/7/365
  • The system must conform to the company marketing graphic language
    and so on and so forth.

These Non-Functional ‘requirements’ can be added to the Product Backlog in a separate section from the Functional Requirements or in a separate ‘document’.

What A PBI Is Not

There was a fashion, that still exists in some places, to have ‘Technical User Stories’; ‘User Stories’ those name technical activities that need to be done; for example:
As a database designer
                                                                         I need to create data access scripts
                                                     So that the product can store and retrieve the data that it needs to use


Such User Stories would just be stating elements of a team member’s work and do not add anything to the understanding of the business needs which the Product Backlog is meant to represent.

It is my strong recommendation that so-called ‘Technical User Stories’ are NOT used because the Product Backlog becomes large, unwieldy, almost impossible to order by business value and prioritisation; the estimated effort for these technical needs are included in the estimation of the ‘business’ PBI; more of which later.

It is true that there may be a need for some activities to set-up the technical environment before the development team can start developing the product, some of which are out of the control of the development team; these activities should take place in parallel with creating the initial Product Backlog.

Creating a Product Backlog

Ordering the Product Backlog

The whole point of Agile is to deliver a product incrementally so that the business can accrue the best value in the shortest possible time.

It, therefore, follows that the product needs to be developed by developing the PBI in the business value order; the highest business value PBI first.

Therefore, the PBI needs to be ordered by business value. I will not go into the techniques for ordering PBI, they are well documented elsewhere but I will give an example, later, of what happened when one team did not use Product Backlog ordering.

Estimating the PBI

We create the initial Product Backlog just after agreeing on the Vision and Objectives and ensuring development viability via the Business CASE  but before development begins; it needs to be estimated in some way to determine how long it may take to develop the product and consequently how much it may cost to develop.

It is a tenet of all Agile frameworks that only the development team is allowed to estimate the PBI.  Once done, these estimates will ‘inform’ the Business Case and analysis can be made to see if the original ‘high-level’ estimates in the initial Business Case are of the same order; a decision can be made as to whether the development is still viable.

Types of PBI estimating

There are 2 generally used types of PBI estimating:

1. Absolute Estimating:  Whereby each PBI is estimated by how much time it would take go from just its name to ‘potentially shippable’ functionality.  Of course, the tasks include analysis, design, construction and testing and what normally happens is that each ‘skill’ will estimate the time it would take for their part in the process and the times summed to get the overall estimate.

2. Relative Estimating:  Whereby the team chooses the PBI which is likely to be ‘the smallest’.

“The smallest in what respect?”  you ask.  The ‘smallest’ does not directly consider time; the PBI criteria that are considered are size and complexity.

However, opinions of size and complexity will vary amongst all team members depending on their skill and experience; what may seem ‘simple’ to an experienced developer may seem complex to the less experienced person.  Similarly, although the analysis and construction may seem simple, the testing may be complex.

For these reasons, it is highly recommended that Relative Estimating is done using ‘Planning Poker’ which is well described elsewhere (see ‘Planning Poker: An Agile Estimating and Planning Technique’); suffice to say here, that once the team have decided which is the ‘smallest’ PBI, they give it a ‘Story Point’ of 1 and all other PBI are estimated with respect to their individual relative size and complexity compared to the ‘smallest’.

So which estimating technique to use?

1. Absolute Estimating can take a long time; it is akin to the traditional way of estimating for the Project Plan.  Also, it has been established that, generally, we are not very good at estimating in time; the larger the thing we are trying to estimate, the worse our estimates get.  However, the technique is familiar to most people and does not require a change of mindset to produce estimates.

2. Relative Estimating requires a totally different mindset amongst the development team members because, initially, not only are they using unfamiliar criteria to estimate the PBI but also, they are estimating in collaboration with other team members with different skill sets and experience.

Despite there being ample evidence that Relative Estimating takes less time overall and allows the stakeholders and development team to focus on business benefit being delivered, because of the ‘difficulties’ of introducing Relative Estimating, many teams revert to time estimation and tracking time.  Also, as we will see in one of the Case Studies below, an organisation’s choice of requirements management tool can make the use of Relative Estimating seem a waste of time for team members.

Another Potential Problem with Relative Estimating

So, having carried out ‘Planning Poker’, the development team now know the total number of ‘Story Points’ that the development represents; not much good to the business stakeholders who want to know how long it is going to take and how much it is going to cost.

On completion of the initial Product Backlog and before development begins, we need to ‘translate’ this total ‘Story Points’ into time.

An Agile Team’s progress is measured by the number of ‘Story Points’ that they deliver in one Sprint; known as the team’s ‘Velocity’.

So we need a knowledge of the team’s Velocity in order to establish an estimate of how long the development is likely to take; for example, if the total number of ‘Story Points’ is 200 and the team’s velocity for a 2-week Sprints is 10, then the estimated time to complete all the PBI is:

         200 ‘Story Points’ / 10 ‘Story Points per Sprint  x 2 (the number of weeks per Sprint) = 40 weeks

However, at the start of an Agile transition, we do not know what the team’s Velocity is or will be.  There are 2 methods to determine what the Velocity may be:

1. The team takes one of the ‘smallest’ PBI (with a Story Point of 1) and does a traditional break down to the tasks involved and estimate those tasks in time;  1 ‘Story Point’ is equivalent to the time represented by the sum of the times estimated for all the tasks
The team’s Velocity may be estimated by:
                                      ‘The number of working days in the Sprint / the estimated days for 1 Story Point’
For example, if the ‘time estimate’ for a PBI of 1 ‘Story Point’  is 1 day:
                                             10 working days in 2-week Sprint / 1 day = Velocity of 10
This velocity can then be used in the formula above to determine the estimate for the potential total time for the development.

2. The development team is allowed to start development for 2 or 3 Sprints taking PBI from the top of the Product Backlog.  At the end of the ‘experiment’ period, the total number of ‘Story Points’ for the completed PBI divided by the number of Sprints completed becomes the Velocity to use in the formula above to determine the estimate for the potential total time for the development.

The potential problem with this method is that management have to release funds for this experimental period without knowing the values to feed into the Business Case to determine whether the product development is viable before development begins.

Once teams have completed 1 product development, we recommend that the team members are kept together for other product developments even though the business area or technology may be different.  Having a team that works well together is more important than creating teams in an ad-hoc manner.  A team’s Velocity varies insignificantly over different product developments and so can be used directly in the formula above to determine the estimate for the potential total time for the development.\

Scoping the Product Backlog

Generally, Agile product developments have strict deadlines so that the major benefits can be accrued; benefits such as competitive advantage, meeting marketing needs, meeting customer expectations or complying with regulations.

Also, Agile teams comprise all the skills necessary to take the PBI from ‘names’ to a potentially shippable product; not all team members are full-time but the team is fixed.

Therefore, generally, the costs for a fixed time product development are also fixed.
Given the classic ‘Iron Triangle’ of development variables:
Scoping the Product Backlog


If we fix time and cost, then the only thing that can vary is the Requirements that are delivered in the fixed time for the fixed cost.

It is quite probable that the initial Product Backlog will contain more PBI than could reasonably be developed in the fixed time available; because the stakeholders/Product Owner has ordered the Backlog by business value, it is relatively straightforward to ‘draw a line’ underneath the lowest PBI in the list that will probably be developed.  We do not remove the lower value PBI because it has been often found during development that a high-value PBI is actually dependant on one of the lower value ones and the ordering has to be amended.

Stakeholders need to understand that even though some requirements (PBI) have been requested, it is probable that they will not be delivered.

But the Product Backlog scoping does not stop there.  The ‘story Points’ for the PBI are estimates and, by definition, they are not accurate.  In the past, to account for ‘inaccurate’ estimates, organisations have added contingency in time and costs to the estimates.

However, in Agile environments where the time and costs are effectively fixed, the development needs some ‘wriggle room’ for when estimates are proved significantly wrong and when requirements change during the development. For an effective Product Backlog, you need to follow Scrum Product Backlog tips.

The Minimum Viable Product (MVP)

The development team must agree with the Product Owner/Stakeholders which PBI represent the Minimum Viable Product, ie what is the minimum to be delivered in the fixed time in order to accrue the minimum benefit required.

There are ‘rules’ how big this MVP can be.  It has been found, from hard-won experience that for a ‘comfortable’ working environment:

1. When a team first starts an Agile transformation they should accept PBI in the MVP which represent around 50% to 55% of the estimated effort; ie if there are 200 ‘Story Points’ in the probable PBI, then the MVP should only contain the highest value PBI whose ‘Story Points add up to between 100 and 110.

2.When the team and the organisation are reasonably Agile-mature, between 9 months and a year of transformation, the team can accept PBI representing up to 65% of the total estimated effort in the MVP.

3.When the team and organisation are fully Agile-mature, PBI representing up to 70% by estimated effort may be accepted in the MVP.  It has been found that no matter how good the teams and organisation are, the variables that come along with all product development make promising more than 70% by estimated effort fraught with problems; the teams must strive not to give stakeholders over-expectations. 

The MoSCoW Rules

Some Agile Frameworks recommend using a technique called MoSCoW to ‘categorise’ the PBI.  The acronym stands for:

  • Must Haves: Those PBI that is essential to the product; equivalent to the MVP above.
  • Should Haves: Those PBI that is important but there is a workaround for them if they not completed in the fixed time
  • Could Haves: Those PBI that might be developed if all the Musts and Shoulds have been completed before the end of the fixed time
  • Won’t Haves:  Those PBI that was initially discovered but was not likely to be completed based on the estimates for the more valuable PBI

“The ‘o’s are just for fun”!

Using the MoSCoW rules allows the Business Case to be prepared with 3 scenarios:

  • The ‘Best Case’ scenario where all the probable PBI are completed; giving the best benefit in the fixed time
  • The ‘Expected Case’ scenario where all the Musts and Shoulds are completed giving the majority of the expected benefits in the fixed time
  • The ‘Worst Case’ scenario where only the Musts are delivered giving only the essential expected benefits in the fixed time.


Case Study 1:

I was working as a business analyst and ‘just-in-time’ Agile trainer/coach for an outsourced team building a replacement system.  The team had 6 full-time business representatives to specify the Agile Requirements (UML Use Cases in this instance).

Creation of the Product Backlog went smoothly; a good ‘To-Be’ Business Process Model was created and Use Cases to be included in the new system were identified; there were 92.

Unfortunately, I was due to go on 3 weeks holiday, so I briefed the team on how to order the Product Backlog and we ran through some Planning Poker with a few of the Use Cases.

When I came back from holiday, I discovered that the team business representatives had had problems in ordering the Product Backlog and had abandoned the attempt because they considered that all the PBI were essential.  Also, the whole team had had problems with Planning Poker because they didn’t know enough about the low-level details.

It had been decided to prototype all the Use Cases before estimation and the developers were split into 3 sub-teams for prototyping and the business representatives split into 3 pairs.

I had taught the team that the prototyping of any PBI should only go through 3 cycles:

1. Investigation where a very rough ‘first draft’ is specified, built and reviewed to make sure that the developers are ‘on the right lines’

2.Refinement where the majority of the functionality is specified, built and reviewed

3.Consolidation where any ‘tidying-up’ was specified, completed and the complete prototype demonstrated to the wider stakeholder community

If it takes more than the 3 cycles, then something is wrong with the detailed process being followed.

The time taken to produce a prototype should be no more than 2 days but it can be as short as 2 to 3 hours if done in a workshop.

Unfortunately, it was decided to pick Use Cases to prototype based on their perceived ‘easiness’ and ‘rotate’ the business representative pairs around the prototype builders such that one pair specified the Investigation, another pair reviewed the Investigation and specified the Refinement and the third pair reviewed the Refinement and specified the Consolidation.
 
At the ‘final’ review, with all 6 business representatives present, the ‘final’ prototypes were significantly different from what was originally specified for the Investigation and ‘recriminations’ took place.  So the prototype developers started again.

It had taken 3 weeks to develop the prototypes for 6 PBI!

I asked the project manager what his estimate was for completing the prototypes for all the PBI; he calculated that the time that would be necessary was 1 month longer than the specified length of the project.

Suffice to say that I worked with the customer representatives to convince them that it would be improbable to complete all the PBI in the fixed time/fixed cost development contract and helped them order the Product Backlog and decide on an MVP. It is worth noting this product development had a Vision, there were no stated objectives nor a visible Business Case.

I worked with the developers and business representatives (who were full team members) to ‘play’ Planning Poker.

Actual development work started one week later; PBI were completed in the fixed time that equated to approximately 70% of the expected business benefit; a further short project was commissioned to bring the expected business benefit up to 90%.

Lessons:

1. Do not go on holiday at a crucial time during the product development lifecycle!

2. If the Product Backlog is not ordered by business value, significant time will be wasted prototyping PBI of low business value

3. If prototyping is to be used, then the whole team should do it together in a workshop; all views will be accessible to all team members and a consensus reached in the minimal amount of time

4. If you are an Agile Project Manager/Scrum Master it is your responsibility to keep the team ‘on track’ and to question decisions that may cause a risk to the project

Case Study 2:

I had been asked to do some Agile coaching for some teams in a global organisation that was undertaking the Agile transformation of one of their divisions to use SAFe®/Scrum; the transformation had been running for 6 months.  There were 4 teams distributed around the globe doing support work to enable 24-hour coverage for this global organisation.

The reasons for SAFe®/Scrum for this transition I covered in my first article.

When I arrived Product Backlog requests were arriving daily to the team members from systems users and the individual team member decided whether the requests were important enough to interrupt the work that they were already doing; the Product Owners were not involved in the decision-making process at all.  As a consequence, there were many requests that had been started and abandoned in favour of ‘questionable’ higher priorities and I discovered that some requests had been sent to inappropriate team members, the work would have been better carried out by members of the other global teams.

Furthermore, although the teams were doing some Relative Estimating at Sprint Planning (not before), they were focusing on time estimates because that was what the requirements management tool required and what management was tracking progress by.  I shall cover the pitfalls of Sprint Planning in my next article.

I started resolving the Product Backlog issues by speaking to all the Product Owners, mostly via video-conferencing, to see if they understood the problems that the current Product Backlog processes were causing.  They did have some understanding but explained that that was the way they worked before the Agile transition and believed that changes to the process were out of their control.

I helped them devise a workable process whereby all requests would be sent to  the Product Owners  at a collective address.  They would take turns during a 24-hour period to determine, with Product Managers, the relative priority of new requests against those already on the Backlog.  In addition, once a week, they would ‘get together’ to decide which team would handle any unassigned requests; ‘show-stopper’ requests would be handled as a matter of urgency and handled by whichever team was immediately available and could resolve the issue before their end-of-day.

By this process, the Product Owners would gain control of the Product Backlog, there would be less questionable priority decisions and there would be fewer ‘disgruntled’ customers.

The process was approved by the Product Managers and all team members apprised of the reasons for the new process and their responsibilities within it.

It quickly became obvious at daily Scrums that not all team members were passing all requests that came to them directly from customers to the Product Owners; the process was reiterated to these team members but then the productivity of some of these members decreased significantly.  The cause was that they were still working on their ‘favourite’ customers requests but not reporting it to the rest of the team.

The Product Owners then had to analyse the central Change Request system for items that had been completed by their teams but had not appeared on the Product Backlog; the Change Request system was not integrated with the Product Backlogs.

Eventually, the ‘lesson’ was learned by ‘miscreant’ team members.

Lessons

1. Without control of the Product Backlog by the relevant authority (Product Owners), it is impossible to police work to give the best business value to the organisation

2. Without control of the Product Backlog, the resolution to some requests may be started and then abandoned in favour of other later requests leaving the customer frustrated

3.Estimating by time at the task level wastes a great deal of time; more of which in my next article.


Conclusion
The Product Backlog is arguably the most important artifact for product development:

  • The PBI must be ordered by business value
  • The PBI must be estimated, preferably by using Planning Poker
  • Its content over time must be controlled by the Product Owner or equivalent
  • Team members must be closely coached and mentored during the early instigation of process change to ensure their understanding of the need for the change and their compliance

Steve

Steve Ash

Blog Author

Steve Ash has been working with ‘Agile’ since 1993 when it was known as ‘Managed RAD’.  He was an early adopter of the DSDM Framework in 1995 becoming a DSDM Board Member in 2002 and was a DSDM examiner.  He is a DSDM Advanced Practitioner and Accredited Trainer/Coach. Steve has since embraced Scrum, Kanban, the techniques advocated by XP, Lean Software Development and Lean Startup. He joined the Agile Alliance in 2002 and is a Certified Scrum Master (CSM), Certified Scrum Product Owner (CSPO), SAFe® Certified Consultant (SPC4) and certified by APMG International to teach Agile Project Management and Agile Business Analysis courses. Since 1996, Steve has trained, mentored and coached hundreds of people in many public and commercial organisations in 11 countries from the USA, through Europe and India to Asia/PAC.
 

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

How To Define Features in Agile Methodology?

Agile projects are known for their simple, iterative approach to cutting through the complexity. Even the most ambitious of Agile projects is taken one step at a time and breaks down complex work packages and tasks into low-level subtasks. Features and capabilities that are needed in the finished product are listed out, and then broken down to manageable chunks which are taken up and completed, one at a time.In this article, we will talk about Features in an Agile project. What are the characteristics of features and how are they applied? How do you build a feature list, and what are the advantages of breaking down features into user stories? Read on to find out!Agile projects are known for their simple, iterative approach to cutting through the complexity. Even the most ambitious of Agile projects is taken one step at a time and breaks down complex work packages and tasks into low-level subtasks. Features and capabilities that are needed in the finished product are listed out, and then broken down to manageable chunks which are taken up and completed, one at a time.In this article, we will talk about Features in an Agile project. What are the characteristics of features and how are they applied? How do you build a feature list, and what are the advantages of breaking down features into user stories? Read on to find out!What is a feature in Agile methodology?A feature is a service or function of the product that delivers business value and fulfils the customer’s need. Each feature is broken down into several user stories, as it is usually too big to be worked on directly. A user story is an informal, short description of a part of a software feature that is written from the user’s perspective and talks about how this particular bit of the feature will offer something of value.Why use features in Scrum and not only user stories?A feature is something that is sizeable enough to deliver measurable value to customers and creates a large chunk of functionality. Features are used to describe the functionality at a macro level, and they are required to create schedules and plan the high-level release of the product.Scrum works on the premise of short development cycles called Sprints, which usually last between 2 weeks and a month but not longer. One feature is typically completed over several sprints. In one sprint, only several user stories can be completed and not, perhaps, an entire feature.What’s the difference between features and epics in Agile?The product backlog is usually detailed into three levels of complexity with respect to tasks. Epics are large quantities of related work that can be broken down into features. A feature, as we have seen, is a service or function that delivers value to the end user. Each feature is broken down into a number of smaller and simpler tasks known as user stories. Do note that for a smaller project, with only around 8 to 10 people on the team, the product backlog may be divided into just features and user stories. Epics come into the picture for large projects with multiple teams who are working over a duration of several years.Who writes the features in Scrum, and what are the steps involved?The Scrum Guide, considered to be the Bible for all things Scrum, does not lay out any guidelines for the use of features.However, Scaled Agile, Inc. indicates that the Product Manager is the owner of the Features, which is to say, he or she finally decides what goes into the feature and what is its priority on the Backlog. The features are not necessarily written by the Product Manager, however, and this could be done by others on the team.On many teams, the Product Manager and the Product Owner are one and the same.There are several steps in the definition and writing of features. Define the WHY, or the benefit hypothesis: What is the functionality that the users gain from the feature? What are the benefits to be gained from implementing this feature? Calculate the business value: Keep in mind the number of users, how often each of them uses the feature, what is the timeframe within which the feature must be released for it to be useful, and how much effort goes into developing this feature. All these together will help to determine the ROI of the feature and ultimately whether it is worth the effort and cost. Features that bring in the most benefit at least cost will be prioritised. Describe the feature: What is the context and how will it be used? What is the need for the feature? Try to include technical details and any information that is important from the Product Manager’s point of view. Write down the acceptance criteria: What are the conditions under which the feature can be deemed to be done? This will help to reduce any ambiguity and mark work progress. How big should the product features be?While there is no hard and fast rule on this, and it is left largely to the convenience of project teams, it is generally agreed that it should be possible to complete a feature within a maximum of three months. When using SAFe, a feature is released in one single program increment. Teams that are working with investor funding and are getting the funds at regular cycles should be able to showcase a completed feature during each investment cycle, in order to demonstrate that they are progressing on track. What are feature points?Feature points represent the amount of the work complexity, effort taken, and knowledge required to complete one feature. They are the same as story points, but in the context of a feature rather than a user story.What are features called in different Agile Methodologies?A feature, while essentially having the same definition, could be called by different terms in different Agile methodologies. In Scrum, a feature is often referred to as a Backlog Item.   In XP, features are called Stories. DSDM terms a feature as a requirement. This could club together several system features. Agile UP defines features in the form of requirements and use cases.What are the characteristics of features?To be effective, a feature should always Offer measurable business value,   Contain enough information to allow for estimation of the work involved, Be small enough to be completed within a program increment or maximum of three months,   Be testable by the scrum team and the product management team.Feature breakdown structure (FBS)When getting into the nitty gritty of detailed planning, agile development uses a feature breakdown structure (FBS) approach that breaks down each feature into smaller, more manageable units of work. This allows easier communication between the customer and the development team, where both can understand each other well in a way that leaves no room for ambiguity. It also helps to track the progress of work against the value that is created. Over time and as the work progresses, the larger features can be broken into smaller features, instead of doing this breakdown all together in the beginning. This way, details are not fleshed out until the time when they are actually needed for design and delivery. Building an initial feature listAt the very start, before the release planning and iteration planning can happen, the team must sit together and list out as many potential features for the system as possible at this stage. Feature requests can come from many sources, and one person should be allocated to collate all these requests. While this could be the product manager, it could also be a customer proxy, a business analyst or someone who is responsible and accountable to the team. The team should refine these requirements, weeding out duplicate items, features that are not possible to implement, and requests that are very vague. As the features are identified, they are added to the list so that they can become a part of the planning processes. This initial feature list can be considered to be a preliminary outline that can be used as input to chart out the release and first iteration. It is not required to wait until all features are defined before getting started on the actual work, and it is also understood that the original list, descriptions, and priorities will evolve over time. Instead of waiting for everything to get detailed out at the outset, the team can get to work with the initial list without wasting any valuable time. As new features which could be critical get identified, they are simply added into the evolving release plan and will get delivered during a subsequent iteration. As the project progresses, the work adapts itself to accommodate new priorities, additional information from stakeholders, and the changing industry dynamics.Advantages of breaking down features into smaller user storiesUser stories, as we have learnt, represent smaller chunks of work while features represent fully formed functionalities of the product. There are many advantages to breaking down the features into functionalities, and the main ones are these: Stories narrow down the focus: Stories are small, doable portions of the work that do not overwhelm the developer. They represent an entire piece of functionality, however small it is, and so can measure incremental progress. Stories fit into a sprint: Features are too large to be completed within a sprint, but stories can be finished within this duration. This allows more efficient scheduling and planning of sprint tasks. Stories capture both intent and outcome: A product manager (who is not required to be technically fluent) can easily describe the outcome of a story to the developer, so that he or she can understand the intent. Stories mitigate the risk: As big stories come with a lot more complexity, they also involve more risk. When features are broken down into smaller stories, this risk is mitigated. Anny erroneous assumptions can be curtailed within a few days rather than several weeks into development. Feature vs. task planningFeatures come into play at a macro level of planning, and it is essential that at a later point they will need to be broken down into tasks and estimated. This is done during sprint planning and release planning.Feature planning and estimates help to schedule releases and iterations. Task planning and estimates help to allocate resources and plan the tasks within an iteration.Since the nature of agile project plans is always fluid and not very precise, feature estimates need not exactly map to a number of task estimates, but there should be a rough approximation between the two.
7362
How To Define Features in Agile Methodology?

Agile projects are known for their simple, iterati... Read More

What Is a Safe Product Owner?

The Scaled Agile Framework® (SAFe®) is, in the words of Dean Leffingwell, Creator of SAFe: “a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, and DevOps.”  © Scaled Agile, Inc. Using SAFe, the process of scaling Agile across a large-scale enterprise can be streamlined. SAFe details out organizational workflows that enhance productivity and employee engagement and ensure customer delight through quick deliveries of quality products.  A key role on a SAFe team is played by the Product Owner. In this blog, you will understand the role of a SAFe Product Owner, and how it relates to that of a Scrum Product Owner. You will also understand the SAFe Product Owner’s role with respect to that of a SAFe Product Manager.What is a SAFe Product Owner?The SAFe Product Owner is the member of the team who works as the voice of the customer. He or she liaises with Product Management and other POs, besides other stakeholders, to define and list out stories in the Team Backlog and order them as per priority.  In an ideal situation, the SAFe PO is in the same office as the rest of the team. However, with today’s distributed teams, this does not always happen. One PO can support up to two Agile teams, at the most. The SAFe PO works with the SAFe Product Manager, who maintains the overall product vision. Key Role & Responsibilities of a SAFe Product OwnerThe main responsibilities of the SAFe PO extend across the team, and even beyond that to participate in Product Management events, where he or she will help to plan and create the Program vision and refine the Program Backlog. The following are the main responsibilities of the SAFe PO: 1. PI PlanningThe PO plays a significant role as a member of the larger Product Management team and has to participate in the events during Program Increment (PI) planning. The activity of program backlog refinement also requires every PO’s participation and close involvement. Before the event, the PO will keep the team backlog updated and will contribute to creating the vision and charting out the roadmap.When the planning event is in progress, the PO should be at hand to give clarity wherever needed. The entire SAFe team will work to map out the team’s PI objectives for the upcoming PI.2. During the IterationDuring the iteration execution, the PO holds extremely critical responsibilities:The PO builds, updates and maintains the team backlog, with updates from all stakeholders and the team. Reviewing and ordering the team backlog as a precursor to the Iteration Planning event is the responsibility of the PO. For this, they may need to coordinate dependencies with other POs.During the Iteration Planning event, the PO gives clarity of user story details, and is around to ensure alignment and concurrence on a final iteration plan. While the team elaborates on the backlog items and creates stories, the PO keeps track of the flow and maintains priorities. POs work with the team to flesh out each story, adding acceptance criteria and acceptance tests, applying Behaviour-Driven Development (BDD) practices. As the work progresses, the PO will work closely with the team to agree on the completion of accepted stories. and see whether they meet the Definition of Done and quality standards that have been laid down. The PO does not need to be a technical expert but should be able to understand the scope of the work that is coming up. He or she should collaborate with the engineers to assist in making decisions and sequencing the technological infrastructures that will enable the business functionality. During team demos, the PO coordinates between the team and stakeholders who are present.   They also participate in events such as the Iteration Retrospective and the Agile Release Train’s Inspect & Adapt workshop, providing the customer’s perspective on the work progress.3. During the Program ExecutionDuring each PI, the PO will connect with other POs to check and coordinate other dependencies, ensuring smooth work progress without any hiccups. They will sync up typically during weekly events. Additionally, POs play a valuable role in creating the System Demo for all the stakeholders involved in the program value stream. 4. Inspection and AdaptationThe Inspect and Adapt (I&A) workshop is held to address any large impediments to smooth progress. During this event, the PO works across teams to see how best to improve processes and increase team velocity and quality. During the I&A workshop, the PO participates in and holds the PI system demo for program stakeholders.SAFe Product Owner vs Scrum Product OwnerBefore we get into the differences in the roles and responsibilities of a SAFe Product Owner and a Scrum Product Owner, we need to also understand a third and more prominent role on a SAFe team: that of the SAFe Product Manager. The SAFe Product Manager is someone who works with several SAFe teams, typically two to four, and owns the Program Backlog—which gives him or her an overall view of the entire project (or the big picture).  The table below talks about the differences in the roles played by a SAFe Product Owner and a Scrum Product Owner.SAFe Product OwnerScrum Product OwnerBacklog ItemsA SAFe Product Owner undertakes the responsibility for the Team Backlog. This lists all the requirements (Backlog items) for the team.A Scrum Product Owner undertakes the responsibility for the Product Backlog. This is a prioritised list of all the requirements for the product.Number of teams they supportA SAFe Product Owner can serve, at most, two teams.A Scrum Product Owner can work with two or more teams.Vision and roadmapA SAFe Product Manager, not the SAFe Product Owner, defines the features and owns the vision and roadmap. A SAFe Product Manager is someone who works with two to four SAFe Product Owners. He or she will have an overall view of the entire program. As such, the SAFe Product Owner exerts less authority than the Scrum Product Owner.Scrum Product Owner defines the features and owns the vision and roadmap. So, as we can see, the Scrum Product Owner undertakes responsibilities that combine those of the SAFe Product Owner and the SAFe Product Manager (but to a smaller scale as the project is typically smaller).Who has the final say on the product?A SAFe Product Owner does not have a final say on what must be done for a certain Product. This is done by the SAFe Product Manager, who is the final authority and owns the vision and roadmap on a SAFe project.It is the Scrum Product Manager who has the final say on what needs to be done for the product.SimilaritiesJust like the Scrum PO, the SAFe Product Owner is also a core member of the team.  He or she is the customer proxy on the team, ensuring that the vision is always kept in focus.They have the responsibility of the Backlog- the Team Backlog in the case of the SAFe PO, and the Product Backlog in the case of the Scrum PO.Both POs work on prioritising the tasks that the team will take up next, guiding them on the relative importance of the stories.Again, both the SAFe PO and the Scrum PO work toward maximizing the product value.They keep an eye on the goal for the next iteration.They participate in reflections and inspect and adapt during and after each iteration.The two roles take part in the Planning, Retrospective and Review of an Iteration in SAFe/ Sprint in Scrum in a similar way.Can one person do both roles in SAFe; that of the Product Owner and Product Manager?The PO and the PM roles are completely distinct in SAFe, and each comes with its own set of responsibilities.There is a different focus for each role: The PM’s role is cantered on the benefits to the customer and the organisation. He or she is also the person with whom the business owners and members of the ART (Agile Release Train) connect. POs always have the needs of their own Agile team in focus.  Product Owners and Product Managers work together collaboratively to understand the customer’s needs and work toward fulfilling them. The flow of information is from the customer to the PM, and then down to the POs and their team members. The POs and PMs meet up at all ART or PO planning and sync up events and stay aligned with the same set of overarching goals. As we have seen, one person cannot undertake the roles of the SAFe Product Owner and the SAFe Product Manager at the same time. POs and PMs must at all times be connected, and work in tandem to deliver a successful product; however, having one person playing both roles is a sure route to disaster!  The last word… The SAFe Product Owner plays a role that is at the core of SAFe, setting up the product strategy, getting deep into customer requirements, and prioritizing the features as per their importance. They hold the responsibility of ensuring customer delight, even as they keep a pulse on the economic value that is to be derived from the product.  In the end, SAFe is all about giving the larger enterprise a framework for scaling Agile — to build better products, respond to volatile markets, and keep in step with emerging technologies — and without the Product Owner’s expertise, all this will fall short. 
9266
What Is a Safe Product Owner?

The Scaled Agile Framework® (SAFe®) is, in the... Read More

Scrum Software for the Ultimate Project Management

Technology has made our lives easier. The number of tools and devices we have at our disposal has made our lives more productive and our work more efficient. The Agile software development methodology has been adopted by several organizations to improve their adaptability, responsiveness, and productivity.  How can we improve the way we incorporate Agile Scrum into our projects? Scrum tools can be the answer. Just like the other gadgets in our lives, Scrum software and tools help improve the productivity of our teams, keep stakeholders happy and help us deliver better products. Before we jump into the use and needs of Scrum software and tools let us understand more about Scrum roles and how they work.Three essential roles for Scrum successThe Scrum Guide defines three pillars of a Scrum team, which include:The Scrum MasterThe Product OwnerThe Development TeamThe Scrum team is a small unit which is self-organised and works towards achieving the same goal; that is, the development and deployment of the product and customer satisfaction.The Scrum Product OwnerThe Scrum Product Owner is among the most essential roles in the Scrum team and acts as a bridge between the stakeholders and the development team. More involved with the business side of the software development process, the PO represents the customer and can be considered as their proxy.  The Product Owner defines the product vision, and, along with the Scrum Master and the development team works towards delivering a product that matches stakeholder needs.The Scrum MasterThe Scrum Master is the servant leader whose main responsibility is to ensure that the Scrum team can perform to the best of its abilities. They do this by overseeing the day-to-day activities of the Scrum team and removing any impediments that may hinder the productivity of the development team. The Scrum Master facilitates stakeholder collaboration along with the product owner and ensures that teams can handle complex environments and deliver projects successfully.The Scrum development teamThe development team generally consists of three to nine people, according to the Scrum Guide. These would include developers, testers, designers and more. The team is allowed to take decisions and decide the length of the sprint and how they will go about it. The development team collaborates to create a high-quality product increment at the end of each sprint that is as per the expectations of the stakeholders.Scrum ceremonies or eventsScrum has five formal events as defined by the Scrum Guide. These events help to validate the Scrum artifacts and implementing them helps enhance transparency. The events are also called ceremonies and are:Sprint PlanningDaily ScrumSprint ReviewSprint RetrospectiveThe SprintWhat Does A Scrum Tool Do?What would you need a good Scrum tool to do? Make your life easier by making processes more efficient and less cumbersome, help you deliver quality products without making a huge dent on your budget, right?  With Scrum topping the popularity charts for Agile project management methodologies, the need for efficient Scrum tools has risen. There are plenty of Scrum tools available that fit the bill and provide interfaces that help teams seamlessly follow Scrum processes and reap its benefits. These tools help:Increase productivityIn task management, daily scrum management  Increase team collaborationIn progress tracking and risk managementScrum Software for the Ultimate ProjectThere are several Scrum software tools that aid in project development using Scrum; not just in technical environments, but in non-technical sectors as well. Software like JIRA, Infinity, TargetProcess, QuickScrum, Wrike etc provide:User friendly GUICompetitive pricingProduct backlog managementTime tracking and calendar tools for schedulingScrum metrics and chartsSprint planning toolsThird party tools for integrationUser story mappingBurnup and Burndown chartsand many more features that will help Agile teams serve their customers better, improve return on investment, reduce costs, enhance collaboration and ensure stakeholder satisfaction. These tools help team uphold the values of Agile and make implementing the Scrum framework easier.Best Scrum ToolsHere are some of the best Scrum tools available in the market:1. JIRAJira is a popular tool used by large organizations to manage their Scrum projects. It has numerous features including customizable scrum boards, reporting features and more. Here’s how teams benefit from this toolCustomizable Scrum and Kanban boardsRoadmaps to communicate with team and with stakeholdersAccess to tools for Agile reportingView of code and deployment statusEnd to end DevOps visibilityEasy scalabilitySecure deploymentDeveloper tool integrationRich APIs to automate processes2. TargetProcessThis tool has been especially designed for teams that want to scale agile. It offers a number of customizable features that make it easy to work with scrum and agile.  Here’s how teams benefit from this tool(Source: Targetprocess Agile Portfolio and Work Management Tool)IdeationBuilt in reports to analyse data and uncover trendsGather ideas across sourcesCloud hosting and on-premise hostingEnterprise grade securityCollaborate across the enterprise  Collaborate with DevOps tools including GitLab, Azure DevOps, GitHub etc3. VivifyScrumThis tool is marketed as an all-in-one solution to manage projects, collaborate and track. Here’s how teams benefit from this tool (Source: Agile Project Management Software - VivifyScrum)Tools to manage agile projects—organize, manage, track and deliverCollaboration boards to effectively collaborate with team and stakeholdersCreate invoices to track and manage business and clientsManage teams and track tasks4. InfinityThis tool is among the most popular in Agile and Scrum organizations due to the many customizations and features it provides. Its various tools help reduce time to market, ensure better quality, improve collaboration and enable customer satisfaction.Here’s how teams benefit from this tool Source: Infinity | Customizable Work Management Platform (startinfinity.com)How Can Scrum Apps Benefit Your Team?The number of Scrum apps and software available in the market for Scrum projects is mind boggling. Which one you choose depends on the requirements of your team and project, and each comes with its own benefits. Some of these benefits include:They help teams, organizations and the product being createdThey ensure better quality by providing the right framework, support mechanism and the right processesAllow for continual improvement by putting in place a feedback loop and sprint reviews by stakeholdersHelp solve impediments and daily issues by incorporating daily testing and product owner feedback into the development processEnsure upfront documentation and help prioritise high value items in the product backlog, thus decreasing time to market.  Quick feedback also helps improve the product and thus helps in continuous improvement.The faster marketing of products increases return on investment, helps tap the market demand and ensures long term benefits for the customer and thus earns their trust for the organizationThe primary tenet of Agile is team collaboration. Scrum software tools help in high level collaboration between the Scrum Master, Product Owner and the development team. Teams can organise, review, plan and discuss everyday tasks, meetings, impediments and more.How to Pick the Best Tool for Your Team?With so many options available, choosing the right Scrum tool for your team can be a tricky task. What you need to do is go through the features of the best tools and see which one best fits your requirements. While the number of features you get will be directly proportional to the money you are ready to pay for the tool, there are some basic requirements your tool must satisfy.Backlog creation:  The very basic format of a Scrum project lies in the creation of a product backlog which sets the pace for the entire project. The backlog is primarily created by the Product Owner with assistance from the Scrum Master and the development team. The tool you choose should help you create the product backlog so that you can prioritise items, define the sprints and identify sprint goals.Implement feedback:  Scrum projects are based on the Agile values of continuous feedback. Your scrum tool should have features which will make your customer’s feedback and requirements easily accessible to you. This will help you implement these changes at the earliest. This continuous feedback loop will help keep customers happy.Sprint creation:  Scrum is iterative and adaptive and works by breaking down projects into small sized sprints. Your tool must aid you in the creation of sprints and burndown charts. These help you keep track of your progress on the project and are essential components of a Scrum project.The other things your tool should be able to do include:Plan and trackCustomise process templatesCustomise dashboards and reportsHelp in time managementHelp create epics and storiesProvide collab and reporting toolsProvide review toolsAnd just like you will create a product that is user friendly, the tool you use also needs to be user friendly for the team. If your team is happy using it, and it makes your life easier and your projects better, then you have the right tool!
Scrum Software for the Ultimate Project Management

Technology has made our lives easier. The number o... Read More

Useful links