Search

Top Product Owner Anti-Patterns & How to avoid them

The Product Owner plays a very critical role in the success of Agile/Scrum implementations in an organization. The entire effort of adopting and scaling Agile across teams is bound to fail if the role of a Product Owner is not understood clearly.  Anti-patterns are practices that go against the spirit of the Scrum Guide, which unfortunately many Product Owners unconsciously fall into. These patterns are in violation of the core principles of Agile, and while each of them seems harmless on its own, in the long run meaningful progress will be hindered.   If you’re a Product Owner and are seeking to improve yourself, you should be aware of what other POs have done wrong, in order to avoid making the same mistakes. This list of some of the most common Product Owner anti-patterns—and the solutions for each—could help! Product Owner Anti-Patterns Busy or Missing Product Owner Product Owners should always make themselves available to the stakeholders, customers, development team and most important, the Scrum Master. This helps important questions to be answered quickly and valuable information to be provided on time. The Product Owner’s availability should never become the bottleneck of the progress of the development team.   Calling the Sprint Review a Sprint Demo During the Sprint Review, the Development Team, PO and Scrum Master figure out whether they are on track and are progressing well toward sprint goals. It is the best time to reaffirm the priorities on the Product Backlog and ensure that value and productivity are being maximised. At this time, a Sprint Demo does not match the importance of the review, and may be out of context.  Expressing the backlog in Technical user stories instead of focusing on business-related user stories While technical functionalities are also important, the User stories should be focussed on business-related aspects. The technical aspects will follow as a natural result of enforcing business requirements. The PO must always prioritise business-related user stories.  Writing detailed user stories When the user stories are too much in detail, there is no scope for negotiation. User stories will evolve over the period of subsequent sprints, and if there is too much of detail in the initial user stories, flexibility is sacrificed. If the user story looks like it is already complete, the development team will not spend time on suggesting improvements, and the stories will not be refined further. They should always be left open ended to increase team engagement.  Questioning the estimates given by the Dev Team The Development team knows their capabilities best, and will be able to provide reasonable estimates of how much time each task will take. A Product Owner who interferes with the estimation is likely to be overstepping his or her boundaries.  Not having a clear acceptance criteria for every story  If there are any user stories that are not defined with the acceptance criteria, it will not be possible to efficiently close out task completion. It would be far easier to make tangible progress if the user story is defined at the start of the refinement cycle, or as close to the start as possible.  Too large user stories As a rule of thumb, a user story should be completed in a maximum of a week or it could become too large to handle. When user stories are too big, the flow of work will be affected and feedback loops will be delayed. User story mapping can be used to slice each story into smaller components.  Not questioning the customers while collecting the requirements It is very important to involve the customers during the process of defining the requirements. They are the end users for whom the product is ultimately intended. When the customers are not included in the conversation, their needs may not be fulfilled. It’s also important to note that in an Agile project, the requirements could evolve over the course of the project, so it’s important to keep the stakeholders in the feedback loop.  Not allowing the Dev Team to work on Technical Debt When dev teams prioritize speedy deliveries over perfect functionality, at a later time the code may need to be refactored. This technical debt needs to be worked on in parallel with sprint deliveries, as otherwise it could pile up toward the end, causing delays in the final product release. A Product Owner should always be mindful of the technical debt and allow the team to iron it out alongside new deliveries.  Not validating the customer’s idea before implementing it While the customers may have specific ideas about what functionalities they need, they are not the experts. The Product Owner, who has sufficient knowledge of the product, should validate their ideas, discuss what is possible and what is not, and then implement the idea if it seems feasible.  Not allowing Development Team members to talk with the Stakeholders directly While the PO is in constant touch with stakeholders, Scrum encourages collaboration. The 4th Principle in the Agile Manifesto explicitly states that “Business people and developers must work together daily throughout the project.” Development teams can also talk to stakeholders to get more clarity, if required. In the spirit of transparency, all such discussions should be made available to everyone so that there is no misunderstanding on any aspect. This is an aspect that should be decided at the outset by individual teams.  Not empowering the Proxy POs In some projects, a Proxy PO is a role created to act as a middleman between the stakeholders and developers. If there is any gap between the PO and the Dev team, the proxy PO steps in and focuses on current features in development. It is important that the proxy PO is sufficiently empowered to be able to perform these tasks effectively, when the PO is unable to do so themselves.  Lack of vision on the product being developed It is the responsibility of the Product Owner to create, manage and own the Product Vision. Unless the PO has clarity on the vision, the product may not turn out to be built as per customer needs.   Delivering more features than valuable features The PO must be aware of which features are the most valuable. If there are too many features being developed, but the most valuable ones are not given importance, then the product will not be as successful. The PO must be aware of which are the most valuable features, and should prioritise quality over quantity.  Not having well-defined prioritization mechanism in delivering user stories It is the PO who, in conjunction with the Scrum team, grooms and prioritises the product Backlog. The Product Owner moves the most important items to the top of the list, and should have a clearly laid out mechanism in place for doing so.  Changing priorities or requirements during the Sprint  If the PO suddenly changes priorities during the middle of the sprint, the development team may have tasks that are unfinished and will lose the momentum of completing them. Considerable time and progress will be lost. While it is a given that Agile is flexible enough to take on changing requirements, unless the circumstances are very exceptional, the priorities should never be changed in the middle of the Sprint.  No single Product Owner, required governance missing in case of multiple POs In the case of a complex project, there could be multiple POs working together. This leads to loss of governance as there could be too many people making important decisions. To be effective, the team should have clear knowledge of who is the PO and who are the proxies.  Missing in Scrum Ceremonies While it is the Scrum Master who facilitates Scrum ceremonies, for complete transparency and smooth communication, it is important that the Product Owner should also be present. The PO should make time to be available at all important ceremonies and events.  Relying on mail communication for answering queries from Dev Team While email communication is always good for complete clarity and maintaining a record, when the PO relies only on emails to communicate with the Dev team, valuable time is lost. Instead, the PO should always be available for urgent queries from the team, and if necessary the responses can be later recorded over email to ensure that there is no misunderstanding.  No emphasis on Quality It is the Product Owner who maintains the Product Vision and should ensure delivery of high quality products. When there is not enough emphasis on improving quality, the Dev team will also lose the required engagement and could churn out substandard work.  Treating estimates as deadlines The core principle of any Agile project is flexibility. When a Product Owner starts to treat an estimated time as a firm deadline, there is loss of flexibility. At times the Dev team may require some extra time to create features with high quality, or the requirements could also have evolved over the course of the project, necessitating an extension of time. The PO should be flexible with respect to time estimates.  Instructing team on what needs to be done, acting as a Manager The Scrum team works in collaboration with each other, and with the PO and Scrum Master to deliver the features during each sprint. There are no managers in Scrum, and the whole team takes ownership for product delivery. If the PO acts as a manager then the spirit of Scrum is lost.  Expecting user stories to be created by team, considering SM and PO to be there only to review the stories While anyone can write user stories, it is the PO’s responsibility to ensure that they are well formulated and organised into a Product Backlog. The Scrum Guide states that it is the PO who is responsible for “ clearly expressing Product Backlog items”, and if user stories are the primary expression of these Backlog items, then it is the PO who must take the ownership of these tasks.   Pushing team to do extra work for finishing everything forecasted during Sprint Planning Agile is nothing if not flexible. During the Sprint Planning process, the team estimates how much work can be completed during the sprint. However, despite best efforts some of these tasks may be rolled over to the next sprint. Pushing the team to complete all the forecasts could reduce quality and increase technical debt, and it is not advised to do so.  Holding the team responsible for any rework post feedback from stakeholders during Sprint Review When there is any feedback from stakeholders asking for changes, it is most often the responsibility of the Product Owner who may have miscommunicated the requirements to the team. In such a case, the team should not be held responsible for the feedback, but the PO should own the responsibility and ensure that there is amicability all around.  Not showing interest in answering team queries for clarifications after Sprint planning A PO should always be available for answering doubts and settling queries after Sprint planning. Failure to do so will cause delays in work, and could necessitate some unnecessary rework.  Not coachable by Scrum Master The Scrum Master is required to act as a teacher, mentor and coach, and in cases where the PO or the team are not aware of the Scrum framework and principles, he or she is required to step in and guide them. If the Product Owner is not conducive to being coached, the project will suffer.  ​Unable to prioritize the work It is the Product Owner’s primary responsibility to prioritize the work, in conjunction with the stakeholders, customers and Scrum Master. He or she must groom the Product Backlog and move the more important items to the top of the list for the next sprint. If the PO is unable to perform this task the way it should be done, then the work will not be executed as per plan and on time.  Consistently changes priorities during the Sprint In an Agile project, it is possible that priorities could change during the course of a Sprint. However, if this happens too often, it is possible that focus will be lost and the team velocity will suffer due to items that are left unfinished. Wherever possible, the PO should change priorities only at the end of each Sprint, rather than in between. Accepting partially completed PBI’s A Product Backlog Item that is partially completed should never be accepted by the PO at the end of the sprint. Instead, it should be re-estimated on the Product backlog to reflect the amount of work left pending, and should be added to the top of the next Sprint Backlog. Work that is left undone creates confusion and uncertainty. It is important that the Definition of Done should be met, before a PBI is mentioned as ‘done’.  Allowing dev team to change the Story points of a user story post implementation Once the team starts work on the user stories, they could be tempted to re-estimate stories. This is a practice that the PO should not encourage. The story point is just an estimate and accuracy is not required. With experience, the team will become more efficient at more precise calculations.  Not saying “No” to the stakeholders and allowing the product backlog to grow in size  It is inevitable that customers or stakeholders will, over the course of the project, keep checking up on the competition. They may want to change the features, add new ones or redefine the product entirely. A Product Owner who is unable to say No when needed will cause the project to go off track.  There's nothing more paralysing than a Scrum team with a bad Product Owner!  The characteristics stated above lead to nothing but a Product Owner “Fishbowl” where new ideas and innovative thoughts pertaining to Scrum processes find no entry at all.  The Product Owner  is.. The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. It’s a one-person role that brings the customer’s perspective of the product to a Scrum Team.   The Product Owner is responsible for:   Developing and maintaining a product vision and market strategy  Product management   Ordering and managing the Product Backlog   Involving stakeholders and end-users in Product Backlog refinement and backlog management   Alignment with other Product Owners when needed from an overall product, company or customer perspective. A GREAT PRODUCT OWNER…   Grasps, shares and spreads the product vision: A great Product Owner acts as the client's voice (also called a proxy-client at times) and makes a product vision together with the stakeholders. Each choice is taken on account of the product vision. This guarantees sustainable product improvement, gives clarity to the development team and expands the chances of product success definitely.  Understanding the customer’s goals:  A great Product Owner truly understands the customer’s goals with the product and is able to outpace their expectations. After all, pleasing the customer is the ultimate goal. Is a good decision maker: A great Product Owner is an authorized person to take product-related decisions. It may take some time to support his/her decisions, but this is an essential condition for an economical pace of the development team Manages the product backlog: A great Product Owner comprehends that the product backlog should be in sequence. Priority, risk factor, quality, getting to learn and dependencies are all considered and balanced with each other. Prefers one-to-one communication:  A good Product Owner believes in one-to-one communication to convey information. User stories are used as a medium of conversation. Knows modeling techniques:    A great Product Owner has a knapsack full of workable modeling techniques and knows when to apply a specific model. Based on the model application he or she drives the project success.  Shares experiences: A great Product Owner offers experiences with peers. This may be inside the organization, or outside it. Conferences and meetings are great approaches to share experiences and garner information. Furthermore, recording lessons learnt can be significant learning opportunities for other Product Owners.  Is present: To be effective, the Product Owner should always be available for discussions with the stakeholders, customers, development team and the Scrum Master.  Claims user story mapping: A great Product Owner should ace the idea of user story mapping. It is a method that enables you to add a second dimension to your backlog. The visualization empowers you to see the master plan of the product backlog. Keeps an eye on functionality: A successful Product Owner keeps an eye on functional as well as on the non-functional aspects of the product. The motto of the Product Owner is to exceed the quality expectations of the customer and enabling functionality that provides value to the product. So, the functionality is the main focus of the Product Owner.   Is knowledgeable: A great Product Owner has a deep product knowledge and comprehends the technicality. Larger products might be difficult to understand and scale. In this case, the PO should know the formula to solve the large queries. Comprehends the business domain:  A great Product Owner knows the ins and outs of the domain. A product should be built with a clear idea of every aspect , not just an understanding of the development needs but also being aware of the current market trends. No matter how great your product is, shipping it after the window of opportunity closes is a waste of time and barely of any value.  Acts on different levels: A great Product Owner is capable of acting on different levels. These levels are popularly denoted as- strategic, tactical and operational. At the board level, a PO should know how to demonstrate the product strategy. Thereafter, he should create a strong support at middle management and facilitate the development team to cope with their daily challenges.  Knows the 5 levels of Agile planning.   Within Agile, planning is done continuously. Every product needs a vision (level 1) which will provide input to the product roadmap (level 2). The roadmap is a long-range strategic plan of how the business would like to see the product evolve. Based on the roadmap, market conditions and status of the product the Product Owner can plan releases (level 3). During the Sprint Planning (level 4) the team plan and agree on Product Backlog Items they are confident they can complete during the Sprint and help them achieve the Sprint Goal. The Daily Scrum (level 5) is used to inspect and adapt the team's progress towards realizing the Sprint Goal. Is able to say 'no'. A great Product Owner knows the best time and way to say “no”. This indeed is a difficult trait to master. While it is easy to give any new idea or feature the nod, there is a flip side. Good backlog management necessitates creating a manageable product backlog with items that will mostly get realized. Appending non-productive items to the backlog will only create false expectations.  Acts as a "Mini-CEO". A great Product Owner basically is a mini-CEO for his product. He or she has a sharp eye for opportunities, focuses on business value and the Return On Investment and acts promptly on all possible risks and threats. Every growth aspect such as size, quality, market share of the product is taken into consideration. Knows the different types of valid Product Backlog items. A great Product Owner can clarify the fact that the Product Backlog consists of more than only new features. For example, technical innovation, bugs, defects, non-functional requirements and experiments, should also be taken into account. Takes Backlog Refinement seriously. A successful Product Owner spends sufficient time refining the Product Backlog. Backlog Refinement is essentially the act of adding detail, estimates and order to items in the Product Backlog. The result should be a Product Backlog that is granular enough and easily understandable. On an average, the Development Team spends no more than 10% of their capacity on the refinement activities. There is no such prescribed approach. The Product Owner can also involve stakeholders and the Development Team in backlog refinement, each for a valid reason. The stakeholders are given the opportunity to state their expectations. The Development Team can clarify functional and technical implications. This will ensure a holistic understanding and enhance the quality of the Product Backlog considerably. Consequently, the opportunity to build the right product with the desired quality will also increase.  Common FAQs A product owner is noticing that overall quality is starting to degrade. What might they do to address the problem? Discuss it with the rest of the team in a retrospective. The Scrum Master who facilitates the retrospective should then help the team to identify the underlying causes and help on how to improve. A possible outcome can be that the Definition of Done needs to be improved, for example a code review can be included. What should happen if the product owner does not accept a story by the end of the iteration? The Product Backlog Item (‘story’) goes back to the Product Backlog. The Product Owner can decide that it needs to be finished in the next Sprint. In the Retrospective at the end of the Sprint, the Product Owner can discuss with the rest of the team on how to prevent this from happening again.  Concluding Thoughts: A Product Owner is indispensable for a functional Scrum team. Not only is the PO the bridge between the development team and the client, but he or she also ensures streamlined product delivery. Ill-defined Product Owner roles and some of the critical PO anti-patterns are some of the impediments many of the Agile organizations are battling at present. The only long-term solution to such persistent issues is clarity on PO roles and a proper understanding of the end-to-end Scrum processes. 

Top Product Owner Anti-Patterns & How to avoid them

2K
Top Product Owner Anti-Patterns & How to avoid them

The Product Owner plays a very critical role in the success of Agile/Scrum implementations in an organization. The entire effort of adopting and scaling Agile across teams is bound to fail if the role of a Product Owner is not understood clearly. 

Anti-patterns are practices that go against the spirit of the Scrum Guide, which unfortunately many Product Owners unconsciously fall into. These patterns are in violation of the core principles of Agile, and while each of them seems harmless on its own, in the long run meaningful progress will be hindered.  

If you’re a Product Owner and are seeking to improve yourself, you should be aware of what other POs have done wrong, in order to avoid making the same mistakes. This list of some of the most common Product Owner anti-patterns—and the solutions for each—could help!

Product Owner Anti-Patterns

  • Busy or Missing Product Owner

Product Owners should always make themselves available to the stakeholders, customers, development team and most important, the Scrum Master. This helps important questions to be answered quickly and valuable information to be provided on time. The Product Owner’s availability should never become the bottleneck of the progress of the development team.  

  • Calling the Sprint Review a Sprint Demo

During the Sprint Review, the Development Team, PO and Scrum Master figure out whether they are on track and are progressing well toward sprint goals. It is the best time to reaffirm the priorities on the Product Backlog and ensure that value and productivity are being maximised. At this time, a Sprint Demo does not match the importance of the review, and may be out of context. 

  • Expressing the backlog in Technical user stories instead of focusing on business-related user stories

While technical functionalities are also important, the User stories should be focussed on business-related aspects. The technical aspects will follow as a natural result of enforcing business requirements. The PO must always prioritise business-related user stories. 

  • Writing detailed user stories

When the user stories are too much in detail, there is no scope for negotiation. User stories will evolve over the period of subsequent sprints, and if there is too much of detail in the initial user stories, flexibility is sacrificed. If the user story looks like it is already complete, the development team will not spend time on suggesting improvements, and the stories will not be refined further. They should always be left open ended to increase team engagement. 

  • Questioning the estimates given by the Dev Team

The Development team knows their capabilities best, and will be able to provide reasonable estimates of how much time each task will take. A Product Owner who interferes with the estimation is likely to be overstepping his or her boundaries. 

  • Not having a clear acceptance criteria for every story 

If there are any user stories that are not defined with the acceptance criteria, it will not be possible to efficiently close out task completion. It would be far easier to make tangible progress if the user story is defined at the start of the refinement cycle, or as close to the start as possible. 

  • Too large user stories

As a rule of thumb, a user story should be completed in a maximum of a week or it could become too large to handle. When user stories are too big, the flow of work will be affected and feedback loops will be delayed. User story mapping can be used to slice each story into smaller components. 

  • Not questioning the customers while collecting the requirements

It is very important to involve the customers during the process of defining the requirements. They are the end users for whom the product is ultimately intended. When the customers are not included in the conversation, their needs may not be fulfilled. It’s also important to note that in an Agile project, the requirements could evolve over the course of the project, so it’s important to keep the stakeholders in the feedback loop. 

  • Not allowing the Dev Team to work on Technical Debt

When dev teams prioritize speedy deliveries over perfect functionality, at a later time the code may need to be refactored. This technical debt needs to be worked on in parallel with sprint deliveries, as otherwise it could pile up toward the end, causing delays in the final product release. A Product Owner should always be mindful of the technical debt and allow the team to iron it out alongside new deliveries. 

  • Not validating the customer’s idea before implementing it

While the customers may have specific ideas about what functionalities they need, they are not the experts. The Product Owner, who has sufficient knowledge of the product, should validate their ideas, discuss what is possible and what is not, and then implement the idea if it seems feasible. 

  • Not allowing Development Team members to talk with the Stakeholders directly

While the PO is in constant touch with stakeholders, Scrum encourages collaboration. The 4th Principle in the Agile Manifesto explicitly states that “Business people and developers must work together daily throughout the project.” Development teams can also talk to stakeholders to get more clarity, if required. In the spirit of transparency, all such discussions should be made available to everyone so that there is no misunderstanding on any aspect. This is an aspect that should be decided at the outset by individual teams. 

  • Not empowering the Proxy POs

In some projects, a Proxy PO is a role created to act as a middleman between the stakeholders and developers. If there is any gap between the PO and the Dev team, the proxy PO steps in and focuses on current features in development. It is important that the proxy PO is sufficiently empowered to be able to perform these tasks effectively, when the PO is unable to do so themselves. 

  • Lack of vision on the product being developed

It is the responsibility of the Product Owner to create, manage and own the Product Vision. Unless the PO has clarity on the vision, the product may not turn out to be built as per customer needs.  

  • Delivering more features than valuable features

The PO must be aware of which features are the most valuable. If there are too many features being developed, but the most valuable ones are not given importance, then the product will not be as successful. The PO must be aware of which are the most valuable features, and should prioritise quality over quantity. 

  • Not having well-defined prioritization mechanism in delivering user stories

It is the PO who, in conjunction with the Scrum team, grooms and prioritises the product Backlog. The Product Owner moves the most important items to the top of the list, and should have a clearly laid out mechanism in place for doing so. 

  • Changing priorities or requirements during the Sprint 

If the PO suddenly changes priorities during the middle of the sprint, the development team may have tasks that are unfinished and will lose the momentum of completing them. Considerable time and progress will be lost. While it is a given that Agile is flexible enough to take on changing requirements, unless the circumstances are very exceptional, the priorities should never be changed in the middle of the Sprint. 

  • No single Product Owner, required governance missing in case of multiple POs

In the case of a complex project, there could be multiple POs working together. This leads to loss of governance as there could be too many people making important decisions. To be effective, the team should have clear knowledge of who is the PO and who are the proxies. 

  • Missing in Scrum Ceremonies

While it is the Scrum Master who facilitates Scrum ceremonies, for complete transparency and smooth communication, it is important that the Product Owner should also be present. The PO should make time to be available at all important ceremonies and events. 

  • Relying on mail communication for answering queries from Dev Team

While email communication is always good for complete clarity and maintaining a record, when the PO relies only on emails to communicate with the Dev team, valuable time is lost. Instead, the PO should always be available for urgent queries from the team, and if necessary the responses can be later recorded over email to ensure that there is no misunderstanding. 

  • No emphasis on Quality

It is the Product Owner who maintains the Product Vision and should ensure delivery of high quality products. When there is not enough emphasis on improving quality, the Dev team will also lose the required engagement and could churn out substandard work. 

  • Treating estimates as deadlines

The core principle of any Agile project is flexibility. When a Product Owner starts to treat an estimated time as a firm deadline, there is loss of flexibility. At times the Dev team may require some extra time to create features with high quality, or the requirements could also have evolved over the course of the project, necessitating an extension of time. The PO should be flexible with respect to time estimates. 

  • Instructing team on what needs to be done, acting as a Manager

The Scrum team works in collaboration with each other, and with the PO and Scrum Master to deliver the features during each sprint. There are no managers in Scrum, and the whole team takes ownership for product delivery. If the PO acts as a manager then the spirit of Scrum is lost. 

  • Expecting user stories to be created by team, considering SM and PO to be there only to review the stories

While anyone can write user stories, it is the PO’s responsibility to ensure that they are well formulated and organised into a Product Backlog. The Scrum Guide states that it is the PO who is responsible for “ clearly expressing Product Backlog items”, and if user stories are the primary expression of these Backlog items, then it is the PO who must take the ownership of these tasks.  

  • Pushing team to do extra work for finishing everything forecasted during Sprint Planning

Agile is nothing if not flexible. During the Sprint Planning process, the team estimates how much work can be completed during the sprint. However, despite best efforts some of these tasks may be rolled over to the next sprint. Pushing the team to complete all the forecasts could reduce quality and increase technical debt, and it is not advised to do so. 

  • Holding the team responsible for any rework post feedback from stakeholders during Sprint Review

When there is any feedback from stakeholders asking for changes, it is most often the responsibility of the Product Owner who may have miscommunicated the requirements to the team. In such a case, the team should not be held responsible for the feedback, but the PO should own the responsibility and ensure that there is amicability all around. 

  • Not showing interest in answering team queries for clarifications after Sprint planning

A PO should always be available for answering doubts and settling queries after Sprint planning. Failure to do so will cause delays in work, and could necessitate some unnecessary rework. 

  • Not coachable by Scrum Master

The Scrum Master is required to act as a teacher, mentor and coach, and in cases where the PO or the team are not aware of the Scrum framework and principles, he or she is required to step in and guide them. If the Product Owner is not conducive to being coached, the project will suffer. 

  • ​Unable to prioritize the work

It is the Product Owner’s primary responsibility to prioritize the work, in conjunction with the stakeholders, customers and Scrum Master. He or she must groom the Product Backlog and move the more important items to the top of the list for the next sprint. If the PO is unable to perform this task the way it should be done, then the work will not be executed as per plan and on time. 

  • Consistently changes priorities during the Sprint

In an Agile project, it is possible that priorities could change during the course of a Sprint. However, if this happens too often, it is possible that focus will be lost and the team velocity will suffer due to items that are left unfinished. Wherever possible, the PO should change priorities only at the end of each Sprint, rather than in between.

  • Accepting partially completed PBI’s

A Product Backlog Item that is partially completed should never be accepted by the PO at the end of the sprint. Instead, it should be re-estimated on the Product backlog to reflect the amount of work left pending, and should be added to the top of the next Sprint Backlog. Work that is left undone creates confusion and uncertainty. It is important that the Definition of Done should be met, before a PBI is mentioned as ‘done’. 

  • Allowing dev team to change the Story points of a user story post implementation

Once the team starts work on the user stories, they could be tempted to re-estimate stories. This is a practice that the PO should not encourage. The story point is just an estimate and accuracy is not required. With experience, the team will become more efficient at more precise calculations. 

  • Not saying “No” to the stakeholders and allowing the product backlog to grow in size

 It is inevitable that customers or stakeholders will, over the course of the project, keep checking up on the competition. They may want to change the features, add new ones or redefine the product entirely. A Product Owner who is unable to say No when needed will cause the project to go off track. 

There's nothing more paralysing than a Scrum team with a bad Product Owner! 

The characteristics stated above lead to nothing but a Product Owner “Fishbowl” where new ideas and innovative thoughts pertaining to Scrum processes find no entry at all. 

The Product Owner  is..

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. It’s a one-person role that brings the customer’s perspective of the product to a Scrum Team.  

The Product Owner is responsible for:  

  • Developing and maintaining a product vision and market strategy 
  • Product management  
  • Ordering and managing the Product Backlog  
  • Involving stakeholders and end-users in Product Backlog refinement and backlog management  
  • Alignment with other Product Owners when needed from an overall product, company or customer perspective.

A GREAT PRODUCT OWNER…  

Grasps, shares and spreads the product vision:

A great Product Owner acts as the client's voice (also called a proxy-client at times) and makes a product vision together with the stakeholders. Each choice is taken on account of the product vision. This guarantees sustainable product improvement, gives clarity to the development team and expands the chances of product success definitely. 

Understanding the customer’s goals: 

A great Product Owner truly understands the customer’s goals with the product and is able to outpace their expectations. After all, pleasing the customer is the ultimate goal.

Is a good decision maker:

A great Product Owner is an authorized person to take product-related decisions. It may take some time to support his/her decisions, but this is an essential condition for an economical pace of the development team

Manages the product backlog:

A great Product Owner comprehends that the product backlog should be in sequence. Priority, risk factor, quality, getting to learn and dependencies are all considered and balanced with each other.

Prefers one-to-one communication: 

A good Product Owner believes in one-to-one communication to convey information. User stories are used as a medium of conversation.

Knows modeling techniques: 

  A great Product Owner has a knapsack full of workable modeling techniques and knows when to apply a specific model. Based on the model application he or she drives the project success. 

Shares experiences:

A great Product Owner offers experiences with peers. This may be inside the organization, or outside it. Conferences and meetings are great approaches to share experiences and garner information. Furthermore, recording lessons learnt can be significant learning opportunities for other Product Owners. 

Is present:

To be effective, the Product Owner should always be available for discussions with the stakeholders, customers, development team and the Scrum Master. 

Claims user story mapping:

A great Product Owner should ace the idea of user story mapping. It is a method that enables you to add a second dimension to your backlog. The visualization empowers you to see the master plan of the product backlog.

Keeps an eye on functionality:

A successful Product Owner keeps an eye on functional as well as on the non-functional aspects of the product. The motto of the Product Owner is to exceed the quality expectations of the customer and enabling functionality that provides value to the product. So, the functionality is the main focus of the Product Owner.  

Is knowledgeable:

A great Product Owner has a deep product knowledge and comprehends the technicality. Larger products might be difficult to understand and scale. In this case, the PO should know the formula to solve the large queries.

Comprehends the business domain: 

A great Product Owner knows the ins and outs of the domain. A product should be built with a clear idea of every aspect , not just an understanding of the development needs but also being aware of the current market trends. No matter how great your product is, shipping it after the window of opportunity closes is a waste of time and barely of any value. 

Acts on different levels:

A great Product Owner is capable of acting on different levels. These levels are popularly denoted as- strategic, tactical and operational. At the board level, a PO should know how to demonstrate the product strategy. Thereafter, he should create a strong support at middle management and facilitate the development team to cope with their daily challenges. 

Knows the 5 levels of Agile planning.  

Within Agile, planning is done continuously. Every product needs a vision (level 1) which will provide input to the product roadmap (level 2). The roadmap is a long-range strategic plan of how the business would like to see the product evolve. Based on the roadmap, market conditions and status of the product the Product Owner can plan releases (level 3). During the Sprint Planning (level 4) the team plan and agree on Product Backlog Items they are confident they can complete during the Sprint and help them achieve the Sprint Goal. The Daily Scrum (level 5) is used to inspect and adapt the team's progress towards realizing the Sprint Goal.

Is able to say 'no'.

A great Product Owner knows the best time and way to say “no”. This indeed is a difficult trait to master. While it is easy to give any new idea or feature the nod, there is a flip side. Good backlog management necessitates creating a manageable product backlog with items that will mostly get realized. Appending non-productive items to the backlog will only create false expectations. 

Acts as a "Mini-CEO".

A great Product Owner basically is a mini-CEO for his product. He or she has a sharp eye for opportunities, focuses on business value and the Return On Investment and acts promptly on all possible risks and threats. Every growth aspect such as size, quality, market share of the product is taken into consideration.

Knows the different types of valid Product Backlog items.

A great Product Owner can clarify the fact that the Product Backlog consists of more than only new features. For example, technical innovation, bugs, defects, non-functional requirements and experiments, should also be taken into account.

Takes Backlog Refinement seriously.

A successful Product Owner spends sufficient time refining the Product Backlog. Backlog Refinement is essentially the act of adding detail, estimates and order to items in the Product Backlog. The result should be a Product Backlog that is granular enough and easily understandable. On an average, the Development Team spends no more than 10% of their capacity on the refinement activities. There is no such prescribed approach. The Product Owner can also involve stakeholders and the Development Team in backlog refinement, each for a valid reason. The stakeholders are given the opportunity to state their expectations. The Development Team can clarify functional and technical implications. This will ensure a holistic understanding and enhance the quality of the Product Backlog considerably. Consequently, the opportunity to build the right product with the desired quality will also increase. 

Common FAQs

A product owner is noticing that overall quality is starting to degrade. What might they do to address the problem?

Discuss it with the rest of the team in a retrospective. The Scrum Master who facilitates the retrospective should then help the team to identify the underlying causes and help on how to improve. A possible outcome can be that the Definition of Done needs to be improved, for example a code review can be included.

What should happen if the product owner does not accept a story by the end of the iteration?

The Product Backlog Item (‘story’) goes back to the Product Backlog. The Product Owner can decide that it needs to be finished in the next Sprint. In the Retrospective at the end of the Sprint, the Product Owner can discuss with the rest of the team on how to prevent this from happening again. 

Concluding Thoughts:

A Product Owner is indispensable for a functional Scrum team. Not only is the PO the bridge between the development team and the client, but he or she also ensures streamlined product delivery. Ill-defined Product Owner roles and some of the critical PO anti-patterns are some of the impediments many of the Agile organizations are battling at present. The only long-term solution to such persistent issues is clarity on PO roles and a proper understanding of the end-to-end Scrum processes. 

Sandeep

Sandeep Kshirsagar

trainer

Sandeep is an Agile mentor with more than 12 years of experience as a Developer, Test Engineer, Automation Engineer, Scrum Master and an Agile Coach. He is presently working as an Agile Coach at Knowledgehut Solutions Pvt Ltd. Up until this point, he has prepared 800+ programming experts and trained more than 450+ programming experts in Agile journey at different organizations.
 

Join the Discussion

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

Suggested Blogs

What Best Describes a Scrum Team?

We are living in an age where speed is the secret to success, and the one who gets the product out first is the winner. In this digital transformation world, organizations that have adopted Agile will succeed; as Agile is all about adaptability, quick delivery and customer focus.  Scrum, the most used Agile framework is all about addressing complex problems through adaptation and value creation. Scrum teams are at the core of a Scrum project. What best describes a Scrum team? Let’s attempt to answer this question.What is Scrum?A term borrowed from rugby; Scrum actually means ‘to huddle’. It signifies how rugby payers huddle together and work as a team in order to gain possession of the ball. Like its namesake in the sport of rugby, Scrum in Agile software development also signifies a process that brings together a team of individuals who work together under complex circumstances to create a product. The term was first used by researchers Hirotaka Takeuchi and Ikujiro Nonaka in their 1986 research paper, "The New Product Development Game."“Scrum is a framework that encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve”—Atlassian Agile coachWhat is the Scrum Methodology?Scrum is a framework under the umbrella of agile development methodologies, along with Kanban, Extreme Programming, Feature-Driven Development, Crystal, and Dynamic Systems Development Method (DSDM).The Scrum methodology focuses on delivering products of the highest quality through effective collaboration between teams involved.  Scrum is based on the three pillars of empirical process control, which are transparency, inspection, & adaptationThe Scrum FrameworkScrum is an Agile methodology framework that follows an iterative and incremental approach for project management, and breaks down large projects into small chunks called epics and sprints.  Each sprint results in the creation of a product and the cumulative effort of all the sprints adds to the improvement of the overall end product. The Scrum framework encourages high level collaboration among team members which comes in handy in tough project situationsWhat is a Scrum Team?Scrum.org is what best describes a Scrum Team by defining it as ‘a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.’ So, in essence Scrum teams are self-organized and highly productive teams that deliver quality products in a highly collaborative environment.  A Scrum team’s success is based on the Scrum values that they share. These are:Commitment:  Commitment is one of the hallmarks of Agile teams. Teams collaborate and work on a common goal through a high degree of communication and trust between them.Courage: Scrum teams must have the courage to fail. Fail fast is a benefit in Agile and Scrum as this helps them discover hidden faults and recover quickly. Scrum teams must have the courage to try new things, innovate, fail and then learn from their failures to ultimately achieve success.  Focus: Having focus is a mandatory requirement of Scrum teams which ultimately helps them limit the work in progress.  Openness: Transparency and openness is also one of the empirical processes on which Scrum is based. Teams that are open and transparent with one another trust each other more and work better towards reaching a successful end point.Respect: Respect between team members is a must, irrespective of the methodology or framework they use. Respect between Scrum Masters, Product Owners and Development team members will help foster trust and enhance collaboration and co-operation between teammates.What describes a Scrum team?A Scrum team consists of three main roles. These are:Development TeamScrum MasterScrum Product OwnerThe development team consists of five to eleven people including developers, testers, architects and others. The Scrum team has a shared goal and through their collaboration and skills of self-organization and motivation, they reach this goal.What is a Scrum Master?The Scrum Master, also known as the servant leader, helps empower the team and guides them on the use of the Scrum framework. Their main responsibility is to ensure that the development team can perform to the best of its abilities, and they do this by removing obstacles or impediments that may hinder the progress of the development team. The Scrum Master is the agile coach and mentor who helps team members understand Agile and its processes and aids in enterprise-wide agile transformations.The Product OwnerThe Product Owner is the bridge connecting the stakeholders and the development team. They define the product vision and through their skills and intelligence drive the project with help from the Scrum Master and the development team. The product owner maintains the perfect balance between the stakeholder and the development team, helping each understand the other’s point of view. They are also well-versed in agile and scrum values and principles and guide the team and well as the stakeholders on the agile ways of working. Creating stakeholder satisfaction is an important responsibility of the product owner and they do this by ensuring that requirements are met, and the product created meets quality standards expected by the customer.The Development TeamThe development team is the driving force of the Scrum project. This team is empowered by the Scrum Master and the Product Owner to take decisions and be as autonomous and independent as possible. At the same time there is a high level of collaboration and transparency among the team members and between the dev team and the Product Owner. The dev team is balanced and helps the product owner manage the backlog and deliver an acceptable product at the end of every sprint.Why is the Scrum team required for organizations?Any organization that wants to go agile and implement projects using the scrum framework has to do so by getting together an efficient scrum team. Scrum has proven to be extremely successful at team levels and it is the Scrum team that drives the project to success. Scrum teams with their collaboration, self-organization, innovation and collocation are able to drive success and business value.A table that summarizes the Scrum Team’s responsibilities in the various Scrum processesScrum PhaseScrum processScrum Master responsibilityProduct Owner responsibilityDevelopment team responsibilityInitiate1. Create Project Vision------2. Identify Scrum Master and Stakeholder(s)--Identifies Scrum Master--3. Form Scrum TeamAlong with the PO decides dev teamAlong with the SM decides dev team--4. Develop Epic(s)Helps PO in developing epicsDevelops epics and arranges user group meetingsHelps PO in developing epics5. Create Prioritized Product BacklogHelps PO in epic refinementRefines epicsHelps PO in epic refinement6. Conduct Release PlanningHelps PO and dev team with backlog prioritization and determining sprint lengthReviews the backlog and develops release planning scheduleHelps PO with backlog prioritization and determining sprint lengthPlan and Estimate7. Create User StoriesHelps dev team and PO write user storiesWrites user stories and incorporates them into the Prioritized Product BacklogWrites user stories8. Approve, Estimate, and Commit User StoriesEstimates the effort required to deliver the product defined in each user storyApproves user stories for the sprintAlong with the SM estimates the effort for each sprint and9. Create TasksHelps dev team break down the stories into tasksHelps dev team break down the stories into tasksBreaks down the approved stories into tasks and create a task list10. Estimate TasksHelps the dev team create the effort estimated task listHelps the dev team create the effort estimated task listCreates the effort estimated task list11. Create Sprint BacklogHelps the PO create sprint backlogCreates the sprint backlog and lists the tasks that need to be completed in the sprintHelps the PO create sprint backlogImplement12. Create DeliverablesGuides the dev teamHelps dev team if neededWorks on creating sprint deliverables13. Conduct Daily Stand-upArranges and conducts the meetingsMay or may not attend the meetingsAttends the meetings and defines any problems or issues faced14. Groom Prioritized Product Backlog Helps PO to groom the backlogUpdates and maintains the backlog continuouslyHelps PO to groom the backlogReview and Retrospect15. Convene Scrum of ScrumsHelps teams collaborate and notes any impediments that may be hindering work--Mentions their progress or any issues they may be facing16. Demonstrate and Validate Sprint Helps dev team in displaying what it has createdApproves or rejects what the dev team demonstratesDemonstrates deliverables to PO and stakeholders17. Retrospect SprintMeets with dev team to ponder on lessons learnt during the sprint. Documents the recommendations--With scrum master retrospect's on sprint and uses the recommendations for the next sprint18. Ship DeliverablesAlong with other team members ships acceptable deliverablesAlong with other team members ships acceptable deliverablesAlong with other team members ships acceptable deliverables19. Retrospect ProjectGets together with other team members and identifies the lessons learntGets together with other team members and identifies the lessons learntGets together with other team members and identifies the lessons learntSo, what best describes a Scrum team? There are many facets to a Scrum team, but the most relatable description would be a highly interconnected and cohesive unit that works together to solve issues. A well-organized Scrum team can raise the ROI of an organization and ensure long term stakeholder commitment.
What Best Describes a Scrum Team?

We are living in an age where speed is the secret ... 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.Three essential roles in a Scrum TeamThe 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

Safe Agile Ceremonies - Expert Guide

“Winners take time to relish their work, knowing that scaling the mountain is what makes the view from the top so exhilarating.” ― Denis WaitleyWhat are SAFe agile events (or) ceremonies? – a brief overview:Before we jump into the topic, could I just take you a step back and remind you what SAFe is all about? SAFe is a way of taking any iterative Agile way of working (normally restricted to a team or few teams) and scaling it up at various levels of the organization, whilst applying a mindset of Lean manufacturing. It also deals with scalability at various levels. Beginning from Essential SAFe right up to Full SAFe, the framework caters to all organizational levels of scaling agility. As part of this, it broadens the core idea of agility mindset beyond just projects/development teams right up to executives/CXOs, who must prepare for enterprise level uncertainties. In a sense, it provides valuable enterprise level scaling insights helpful for the executives to tackle any uncertainties/risks associated with a project.As you start applying SAFe in your organisation, it is important for you to understand how each level works in conjunction with the other, depending on how mature your SAFe enterprise is. The key link between these levels is the SAFe specific events which help with smooth value delivery facilitation. The events help with alignment across teams, ARTs etc thus helping in managing risk by providing a level based cadence and synchronization.Essential SAFe - Your First Level of Scaling Using an Agile Release Train (ART). Courtesy © Scaled Agile, Inc. Source: Scaled AgileWhy do we need level-based ceremonies?While it is important to go through your team level events (like the 4 sprint events if you are doing scrum etc.) it is important to have the scaling events that help with bridging gaps and unblocking dependency between teams. The most important part of these SAFe specific events is for ‘Business Stakeholders’ to get a look (demo) at a proper incremental product and thus the value arising out of it. Makes sense? It did for me and let me tell you why.I was once associated with 3 feature teams, who were working towards a common product goal. They all had the same business stakeholders but were working on individual features. Team A was working on developing a Login page, Team B was working on a landing dashboard while Team C was hopping along, trying to provide a search functionality for the user. All of them were applying the Scrum framework and were running their own events. Sprint demos were happening individually and were being represented by the Product owner separately along with his business analysts. All seemed fine but there was a nagging problem. The product owner was worried, because he couldn’t bring any business stakeholder to view the demos, as they were being run in silos and there was no visibility on the incremental product. Well technically there was, but they would have to sit through three or four-hour events individually to get bits and pieces of the product demo. In the real world, it's not a possibility simply because your business stakeholders will not have that much time to spend on multiple demos. It is not a good use of their time either. So, what’s the solution? Simple, it’s SAFe to the rescue! Let’s try and understand how the SAFe specific events help with this.Prescribed PI Cadence for Various Levels of Scaling. Courtesy © Scaled Agile, Inc. Source: Scaled AgileHow do the events (or) ceremonies help to scale up according to the levels in SAFe:SAFe is very relevant and designed to thrive in situations where there are significant cross functional dependencies between agile teams and support / functional teams (infrastructure teams, architect community etc).  Essential Level:   As you start to scale up one level up, you will be working with anywhere between 5-12 agile teams who will all be collectively working towards a common goal which is the program increment or PI. The anchoring catalyst that brings them all together is your ART (Agile release train). Before getting into the events, lets understand the various roles involved at this level because this is the common denominator across all levels of SAFe and across organizations. This is where you need to get it right without which there is not much use in scaling higher. Key Roles involved: Release Train Engineer (RTE) System Architect/Engineer Product Management   Business OwnersPrescribed events on a typical Agile release train (ART). Courtesy © Scaled Agile, Inc. Source: Scaled AgilePI PlanningAccording to me, PI planning (hands down) is THE most significant aspect of executing this framework. This is where all the magic happens. It is sometimes referred to as the heart of the framework as it offers a clear vision of what the program increment needs to be, what the cross-team dependencies are and how they bring together the cultural sustainability much needed within the release trains. It is so important, that if carried out incorrectly it could lead to several ambiguities, development challenges and mostly a disastrous product increment. However, when it works well, the iterative cycle serves to flesh out the crucial elements of the plan and the processes ensure buy in from the stakeholders.Duration: A normal PI planning is a 2-day activity, which is a face to face cultural get together of the various ART teams. However, a new 3-day distributed PI planning has been introduced to help with geographically distributed teams (across various time zones), very apt for the current pandemic situation.“There is no magic in SAFe® except maybe for PI Planning”. – The authors of the SAFe framework.In big organizations with multiple distributed teams across multiple vendors, work streams etc. it is almost impossible to run these teams independently, whilst still having to deliver an incremental program. SAFe via the PI planning exercise mentioned above, helps with sorting out these issues by recognising cross team dependencies upfront, constantly negotiating & visualising them. This doesn’t just stop with the PI planning but the framework also proposes a cadenced way of continuing this via the scrum of scrums. The Program Board is an ideal way to showcase the cross-team dependencies.A sample SAFe Program board. Courtesy © Scaled Agile, Inc. Source: Scaled Agile1. Inspect and Adapt (I&A)An inspect and adapt event is scheduled after every PI. This event is dedicated to aligning to the principles of Kaizen, which simply means to change for the better. The events contain self induced thought processes to revalidate your assumptions that everything is working OK. The I&A event consists of three sub-parts as below:  PI System DemoQuantitative and qualitative measurementRetrospective and problem-solving workshop2. ART Sync Agile release trains tend to apply a cadenced synchronization process to help manage the ability to focus on continuous value delivery. An ART sync will typically comprise of the below sub-events.  Scrum of Scrums: This event is for representatives from all the teams on a release train to come together in a regular cadenced manner, especially on large ARTs. This is normally facilitated by the release train engineer (RTE) and will involve scrum masters of the individual teams and a few selected team members (authorised by the team). The sole purpose of the SoS calls are to understand progress towards the common goal, validate cross team dependencies and unblock impediments that may arise out of them. Duration: The length and frequency of the meeting will depend on a few factors like the size of the ART, the release frequency, type of features being worked on, ability to decouple releases etc. For e.g an ART which releases features into production every 4 weeks might want to have an SoS call every 2 weeks for about an hour. Again, if this doesn’t work for you, just inspect and adapt to what works well for your organizational needs. Just make sure that the SoS is utilised for its sole purpose and not just status updates as depicted in the below comic representation.Scrum of Scrums PO SyncThis event is represented by the Product Owner, business analysts and the product management group. This is used mainly to level up the product backlog refinement and for clarifying PI (Program Increment) scope, reviewing roadmaps and grooming for the upcoming PIs.Duration: Very similar in concept to the SoS, so just follow what works for the group. 3. System DemoAs part of a common understanding towards delivering incremental software, shortly after each iteration in the PI, there is a system demo scheduled. Work completed across all teams from the release train are compiled in a stable environment before it is reviewed by the business stakeholders and other important sponsors who may have a keen interest in the product. This is on top of the individual team level demos that happen after each iteration.Duration: Anywhere between 2-3 hours that will allow time for a demonstration of the program increment in a collative manner, on top of what has been delivered from the previous PIs as well.In case your ART is pretty small, then you may want to have just have some of the events combined into a more generic ART sync, where all roles come together to collaborate towards the program increment. This can sometimes occur if the ART is focusing on a particular value stream, confined to limited business functionality, rather than elaborate features.Solution/Portfolio LevelsAs you scale higher, the processes and events become much less prescriptive. There is a good reason for this because the focus at this level is not just on having repetitive demos that have already happened before but on building thought leadership around business outcomes and enhancing business agility. Which is why we will not be diving deep into that in this blog. But let us look at the events that occur at the macro level.Lean Budget Review  Idea Sharing via Communities of Practice (not a formal event but a collaborative group)Solution DemoPortfolio SyncRoadshowWhat are the benefits of SAFe Agile ceremonies?:The Magic of PI planningWell, the more I talk about this, the more excited I am. A PI planning event when carried out to its truest purpose, gets half the job done. Here is where most of the brainstorming occurs and business value gets determined and, in some cases, gets assigned in a quantifiable manner to user stories and helps with the prioritisation.PI Planning Synchronisation towards a common goalThe events are a constant reminder that all teams are working towards delivering incremental value either on a particular value stream, or feature or program. An RTE and Product Management will help reiterating the need to focus on the larger goal whilst helping sorting out inter team dependencies.Less prescriptiveAs is the framework itself, SAFe events/ceremonies are less prescriptive. An SPC would recommend, apply the principles but inspect and adapt as to what works for your organization. As per the example I provided earlier w.r.t to the duration of the SAFe events, start with something reasonable and then validate its effectiveness. Then leave Kaizen to do the rest.Visualization of incremental value deliveryOpportunity for Business stakeholders and sponsors to have a look at the overall program increment every iteration, thus helping them evaluate the progress and provide timely feedback on market trends. What are the common mistakes?Lack of a shared product visionThings can go wrong if there is not enough representation in the product management group, say for e.g at the PO Sync event. This can lead to a blurred product vision with each team working out of sync. This may ultimately get detected too late, probably at the time of the system demo, and lead to a whole lot of unwanted rework.SoS as a status updateThe Scrum Of Scrum event should be used as an event to unblock cross team impediments or dependencies and not to just update what each team has been doing or is doing in its current sprint. TimeboxingGiven the scale at which these events will be conducted, it is critical that the associated events are facilitated in a timeboxed manner or else the participants could end up sitting and talking for hours. Roles like RTE, SPC Coaches etc will be critical in addressing this issue.Remote facilitationLack of effective collaboration tools could lead to some disastrous situations whilst facilitating the SAFe events. Given that most teams are running virtual ceremonies/events at the moment, its crucial to establish a working distributed model. This will then ensure that the platform is set up for the most effective collaboration and cross-functional work to take place.While you try to scale, as per the implementation roadmap, its essential that you solidify the process around which your ARTs will be functioning. It’s like setting the railway tracks with the correct track gauge matching the configurations of the wheelsets of the trains that will run on them. If not, they will just derail. As your ARTs pass through your set process, they will only benefit by sustaining focus and pace while moving towards a successful incremental product delivery.Thanks for your patience and wish you all the very best in your Agile journey. In case you want me to write about any specific topic, please feel free to comment below and I’ll be more than happy to add them to my ‘Blog Backlog’. If you liked the article, please do share it among your agile community to help spread the word.  Hope to see you soon, with more such interesting topics.
Safe Agile Ceremonies - Expert Guide

“Winners take time to relish their work, knowing... Read More

Useful links