• Consultancy
    • Digital Transformation
    • Organisational Agility
    • Digital PI Planning
  • Agile Training
    • Scaled Agile (SAFe)
    • Scrum Training
  • Agile Teams
  • Tooling
  • Insights
  • About Us
    • Our Work
    • Contact
    • Join Us
AgilicistAgilicist
  • Consultancy
    • Digital Transformation
    • Organisational Agility
    • Digital PI Planning
  • Agile Training
    • Scaled Agile (SAFe)
    • Scrum Training
  • Agile Teams
  • Tooling
  • Insights
  • About Us
    • Our Work
    • Contact
    • Join Us

SAFe

  • Home
  • Blog
  • SAFe
  • Why Should Teams Write Objectives?

Why Should Teams Write Objectives?

  • Posted by Admin
  • Categories SAFe
  • Date 2019-12-09
  • Comments 0 comment
Agile team objective

One of the most often misunderstood (and often skipped) parts of the PI process is that of Objectives writing.

The bit people get wrong is knowing the difference between objectives and features. At best, teams resort to paraphrasing their features into business language.

Having driven scaled agility across several organisations, the importance of PI objectives cannot be understated. In our experience their proper use does three key things:

1. Validates Understanding2. Focuses on Outcomes3. Summarises Data

1. Validates Understanding

An inherent challenge in software development has been ensuring that the stakeholder articulates their requirements and these requirements are effectively passed to the development team who in turn interpret them as intended.

The use of PI Objectives helps create an immediate feedback loop from the teams back to stakeholders and provides the opportunity to quickly validate the team’s understanding of the desired outcomes. The challenge for the teams when writing their objectives is: ‘Can you convey concisely in easy to understand language, the value sought by implementing these features?’

By summarising the intent and outcomes that the business wants to achieve the loop of understanding is closed and any misunderstandings are exposed through conversation before any development work has started. The understanding between the team and business creates alignment and gives confidence that the money invested over the course of the next 10-12 weeks is money well spent.

2. Focuses on Outcomes

Features and their acceptance criteria help teams to capture, understand and collaborate on the actual development work. But frequently this is a focus on the work itself without an understanding of the overall outcome. This leads to missed opportunities, with teams overlooking potentially valid, architecturally sound solutions because they already have a preconceived notion of how that value should be delivered.

Is the goal to complete the list of features, or is it to provide the outcomes desired by those features? If the same (or more) value could be achieved with half the amount of work, without completing all the features, is that acceptable?

By understanding the business intent and through direct conversations with stakeholders teams have the opportunity to offer new perspectives and apply their expert knowledge most effectively.

3. Summarises Data

Despite our objections, we have seen large trains consistently take on more than 40 features per PI. This in itself presents its own problems, but it is clear that with so much ‘stuff’ being planned that nobody except the Product Manager has read every Feature carefully, and certainly nobody outside of the train has read them all. In this regard, PI Objectives provide a summary of intent and are a useful way to provide clear evidence of progress to those within, and outside of the train. Their use can augment quantitative reporting and provide a compact way to convey the same information as a feature completeness report.

In conclusion, PI Objectives should not simply be viewed as ‘part of the process’. If they are used in the proper way, they can improve alignment between business and development, help the organisation become more nimble through decentralised decision making and provide valuable insight into true progress.

Tag:agile teams, team objectives

  • Share:
author avatar
Admin

    Previous post

    7 Pitfalls to Agile Testing
    2019-12-09

    Next post

    Do I need to renew my scrum master certification?
    2020-07-22

    You may also like

    ashkan-forouzani-v31lgBn5114-unsplash
    Is The SAFe Framework worth doing?
    20 January, 2016

    Leave A Reply Cancel reply

    Your email address will not be published.

    Latest Posts

    Rowing boat
    Six reasons behind a small team size
    20Jan2016
    Is Scrum collapsing?
    The Death of Scrum
    29Jul2020
    Should I renew my certification?
    Do I need to renew my scrum master certification?
    22Jul2020

    Categories

    • Agile
    • SAFe
    • Scrum
    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
    Necessary
    Always Enabled

    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.

    Non-necessary

    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.

    • 02033222296
    • info@agilicist.com