Prioritisation – where to startPrioritisation – where to startPrioritisation – where to startPrioritisation – where to start
    • Our Expertise
      • Increase Effectiveness
      • Align & Focus
      • Agile Leaders
      • Autonomous Teams
    • Our Offer
    • Our Achievements
    • Our Blog
    • About Us
      • Contact Us
    • 4 Pillars
    • Academy for Agile Coaches
    0

    0 ₫

    • Academy Login

    Prioritisation – where to start

    • Home
    • Insights
    • Organizational Effectiveness Adaptive Organizations
    • Prioritisation – where to start
    Published by Chris Kruppa on December 19, 2017
    Focus on Outcome

    How can I give a good prioritisation to get everything done?

    I wish, the day would have more than 24 hours.

    This is my third all-nighter this week.

    I have too many ideas for too less time per day.

    Most of us probably have heard one or more of the quotes above. We usually feel we do not have enough or need to work overtime to accomplish everything we planned. But of course those ideas and quotes above are wishful thinking. Then a day will never have more than 24 hours. Therefore prioritisation is the key.

    The myth of doing everything

    Human beings are generally very bad in planning – the longer we plan, the harder it gets for us. When we plan, we usually assume the most perfect situation and having the answers to everything. Software teams give us a good indication on our ability to plan. Most of us complained at least once about their “bad estimations“.
    We look at a day of 8 hours and we squeeze in, what we want to achieve. In the end we wonder, why most of the time we did not achieve this. One of the problems is our inability to plan for slack and thus not able to navigate our planning in accordance with urgent activities coming in. In the end we just do overtime in order to accomplish our plans.

    The concept of flexible scope

    As mentioned, the overwhelming majority of us will not be able to stretch the day to more than 24 hours. It is important, not to do everything, but the most important of what we planned. Scrum introduced the concept of flexible scope, in which we value the timebox and cost (stable team) over our plan. We rather inspect and adapt on our working software. We also discussed this in our blog article about the 10th principle of the Agile Manifesto of Software Development.

    Foundations of prioritisation: Important vs. Urgent

    The higher in the hierarchy you are, the more stakeholders are around you and will push for their activities. But it is first of all important to differentiate: Urgent does not always mean it is important. Customer Facing roles such as Customer Success / Client Solutions are usually the loudest when it comes to push for the agenda of their tasks. They say, the customers request them. Does this mean, they are the most important tasks?

    Organisationally we can label important tasks as more strategical or tactical activities while urgent tasks are more operational activities. Both are important. Strategies set broader activities to achieve your vision. But the operations will be manageable and usually obvious activities to support this strategy. The problem is, that in our daily work and teams, it is hard to understand, what really urgent ist.

    Urgent vs. perceived urgent

    I usually differentiate urgent activities from perceived urgent activities. This will give you usually a good indication for your prioritisation. Focus on real urgency – not perceived urgency. The difference in those activities will be the different result. One will create happy customers and one will make customers happy. As we know from Ash Maurya’s book Scaling Lean, happy customers are more sustainable as they will refer you to their network thanks to the received value.
    Instead of just reacting to an “urgent task”, I recommend to first stop a minute, breathe (;-)) and ask yourself some important question, before you sacrifice part of your (un-)planned slack time:

    • Who requests that? A client? A key account? How many clients?
    • Would it make the service sustainable better?
    • If we do not react, would the client leave us?
    • Would a client recommend us or upgrade the service, if we do react?
    • What would be the impact to wait another day / week / month?

    Those 5 questions are usually answered within a few second. If you cannot really expect any implications out of the received answers, it is probably a perceived urgency over a real urgent issue. Most of the time, we deal with perceived urgency.

    Example: Service Level Agreememt

    Most organisations who create products are having a defined approach how to deal with clients in case the product delivery fails. I have seen Service Level Agreements (SLAs) trying to cover all eventualities with up to 7 different classification of bugs. These organisations create big quality assurance and customer success teams in order to deliver their promise of the SLA. In the end nobody is not delivering new features, but everybody is just trying to please every eventuality of any customer.

    I therefore recommend basically three level of incidents:

    1. Major Blocker: Customer cannot use a core function of the system – Suggested action: Stop everything you do and fix it immediately.
    2. Minor Blocker: Customer can use a core function only through a workaround – Suggested action: Work on it in your next slack time. By latest  pick it up on the top of your next Sprint Backlog.
    3. Everything else: It goes into the product backlog and can be evaluated by PO in discussions with stakeholders (We will discuss a technique on how to prioritise your product backlog in an upcoming topic).

    A member of any product company probably would agree, that most of the incidents are of the third category. Some might fall intosecond category, but the least incidents will be of first category.

    But I am not in a product company

    The concept also works, if you are not working in product company. The message is not to organise your urgent activities, but to focus on an agreement with your stakeholders on when you would deliver. There you will find out something astonishingly. Most stakeholders are fine with how you plan your activities as long as you are transparent about them. And of course as long as you can deliver on your promise in 80% of the cases.

    Stress is mostly the result of your reaction to certain situations and not how others make you react to it. As long as you deliver on Tuesdays when you promised to deliver on Tuesday, stakeholders are fine. If you are unsure about that, then don’t promise Tuesday, but Wednesday. If you deliver in the end a day earlier, there will be nobody who will be angry about it. Prioritisation has less to do how you can make your customers happy, but how you communicate them.

    Share
    Chris Kruppa
    Chris Kruppa
    Chris is a German working in Vietnam since 2008. He became passionate on Agile, when he started to implement Agile into his Marketing team about 2010. He immediately saw the impact of cross-functional and transparent teams and became a CSM in 2011. He founded semdi solutions in 2012 with the goal to coach teams on how to be more adaptive and ready for the 21st century. Since then, he has worked with nearly 20 organizations in Southeast Asia and supported them in increasingly becoming more Agile.

    Related posts

    Role of Company leaders in an Agile journey to HIgh-Performance Teams
    January 11, 2023

    Harnessing High-Performance Teams Through Agile Principles


    Read more
    What is Agile? True Agile is rarely visible in it's process
    January 5, 2023

    Agile: More than Just a Framework


    Read more
    Portrait Photo of Woman in Red Top Wearing Black Framed Eyeglasses Standing In Front of White Background Thinking
    December 13, 2022

    Making the most of Scrum: Avoid these Misconceptions


    Read more

    Leave a Reply Cancel reply

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

    Logo semdi solutions

    semdi solutions Co. Ltd.

    Level 14, Saigon Center 1
    65 Le Loi
    Ward Bến Nghé, District 1
    Hồ Chí Minh City

     
    • Contact
    • Imprint
    • Privacy Policy
    semdi solutions, © 2022
      0

      0 ₫

      • Academy Login
      ✕

      Login

      Lost your password?

      We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
      Read More about our privacy policy
      Cookie SettingsAccept All
      Manage consent

      Privacy Overview

      This website uses cookies to improve your experience while you navigate through the website. Out of these, 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 affect your browsing experience.
      Necessary
      Always Enabled
      Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
      CookieDurationDescription
      _GRECAPTCHA5 months 27 daysThis cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks.
      cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
      cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
      cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
      cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
      cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
      cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
      viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
      Functional
      Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
      CookieDurationDescription
      ppwp_wp_session30 minutesNo description
      Performance
      Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
      Analytics
      Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
      CookieDurationDescription
      _ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
      _ga_8T1CV8HV5N2 yearsThis cookie is installed by Google Analytics.
      _gat_gtag_UA_28003764_11 minuteSet by Google to distinguish users.
      _gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
      _gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
      Advertisement
      Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
      CookieDurationDescription
      test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
      Others
      Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
      SAVE & ACCEPT
      Powered by CookieYes Logo
      Pre-register for our 4 Pillars Guide

      "*" indicates required fields