Simplification Officers

What is all this Collaboration about? Collaboration From Another Perspective Unfortunately we see many Agile teams using their Sprint Planning to task out everything that needs to be done so that every single individual knows what he/she needs to do and for the rest of the Sprint no true collaboration is needed. That's not what collaboration in an Agile world is about is it?! Let me quickly explain collaboration from another perspective.

Small or Low Numbers versus the Predictability in Forecasting The fallacy of the low numbers and how it affects the predictability within your forecasts explained. Providing some insights how buckets, man days, man hours could affect your plan and how to go about them differently. Providing some insights how to grow the overall predictability within your forecasts for small, medium and large organisations. Especially good information to absorb by Product Owners, Product Managers & others with high interest in deadlines

How do you deal with low performers in your team? A topic many, more often would like to ignore instead of tackle. Here is one way to deal with it: https://lnkd.in/enCqkNzz #SimplificationOfficers #GrowSkills #Cleanup

You should expect the use of Scrum to become more successful when the Team lives the Values of commitment, courage, focus, openness and respect. Then empiricism starts to work and trust is being built. 👉 The more people become proficient in living the Scrum values, the more successful the use of Scrum will be. Each of the team members should live these values. So how can the Developers show this? - Commitment to deliver the quality that is needed by the users. Nothing more, as this would be too expensive for the user, nothing less as this would not be beneficial to the user. - Have the Courage to plan for less to deliver more. Plan less features / items, deliver more - the expected quality for these items. - Focus on the Sprint Goal. Everything else gets in the way. If something does not support the Sprint Goal, how important can it be to work on anyway? Focus on the Definition of Done, which is the quality goal for the team. Quality not achieved = Sprint Goal not achieved. - Have the needed Openness to your colleagues. If you don’t find a solution to a challenge, say so. Your colleagues will help as you are all working towards the same goal. - Respect those with whom you work. An at first sight silly idea might turn out to be just what the team needed. You’ll probably only find out by doing. These are only one example of how each Scrum Value could be lived by the Developers. Summary: Using the Scrum Values as a guide for the Scrum Team how to behave during the entire Sprint will support raising trust. Without trust there will be a low level of transparency - the cornerstone for Scrum. The more the team becomes skilled in living the Scrum Values, the more transparent the Increment will be. Prompt Together with your Scrum Team, evaluate how the Developers can live the Scrum Values even better. How do you see that the values of Commitment, Courage, Focus, Openness and Respect are lived? What can you do to make the Scrum Team live these even better? We hope you will find value in these short messages and if you are looking for more clarifications, feel free to take contact. Interested in more? Watch out for upcoming posts. Don't want to miss any of these posts? You can have them weekly in your mailbox via https://lnkd.in/dmyDEqm I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact. #Scrum #Simplification #BoostYourScrum

Growing from startup to unicorn? Need to grow the amount of teams working on your product rapidly? Started an adoption and now in need to onboard new teams? Check out this short video explaining how I deal with these situations, especially from a product backlog perspective. https://lnkd.in/egmsRQQv

You should expect the use of Scrum to become more successful when the Team lives the Values of commitment, courage, focus, openness and respect. Then empiricism starts to work and trust is being built. 👉 The more people become proficient in living the Scrum values, the more successful the use of Scrum will be. Each of the team members should live these values. So how can the Product Owner show this? - Commitment to truly understand the users of the product. What are their real challenges, their frustrations? What keeps them awake at night? What are their hopes, their dreams, their desires? - Have the Courage to say No. Not every request is to be added to the product or service. It is OK to say no to a user if as a Product Owner you are convinced this request is not providing enough value or does not match the vision of the product. - Focus on the Product Goal. Don’t distract yourself nor the team. Set a goal and go for it. Keep evaluating the goal that it still makes sense, and keep the focus on it until it is proven reached or no longer valuable. - Be Open to your users; to your market. Listen carefully to understand. Also be open to share insights you got from other users. Be open to reevaluate the order in the Product Backlog, and even adapt the product vision. Listen and share. Listen and adapt. - Respect your users and your team. They sometimes will tell you things you didn't want to hear. Users not yet satisfied with the product - why is that? Team members indicating unrealistic requests - why is that? Respect their opinions and go into a constructive conversation. These are only one example of how each Scrum Value could be lived by the Product Owner. Summary: Using the Scrum Values as a guide for the Scrum Team how to behave during the entire Sprint will support raising trust. Without trust there will be a low level of transparency - the cornerstone for Scrum. The more the team becomes skilled in living the Scrum Values, the more transparent the Increment will be. Prompt Together with your Scrum Team, evaluate how the Product Owner can live the Scrum Values even better. How do you see that the values of Commitment, Courage, Focus, Openness and Respect are lived? What can you do to make the Scrum Team live these even better? We hope you will find value in these short messages and if you are looking for more clarifications, feel free to take contact. Interested in more? Watch out for upcoming posts. Don't want to miss any of these posts? You can have them weekly in your mailbox via https://lnkd.in/dmyDEqm I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact. #Scrum #Simplification #BoostYourScrum

Check out this video where we delve into the pivotal role of management in driving successful transformations. We explore the transition from traditional management practices to agile methodologies, emphasizing the importance of trust and adaptability. The discussion highlights how managers can effectively support their teams in a multi-team Scrum environment, offering strategies to balance old and new ways of working. Through insightful dialogue, we try to illuminate the path to a more collaborative and efficient organizational culture. We share practical advice for managers looking to guide their teams through agile adoption. This video is worth the time for anyone keen to understand the evolving landscape of agile management and leadership. Tune in to gain valuable perspectives and actionable strategies for fostering an agile culture. 🎥 https://lnkd.in/enKfMXWW 🎥 #Leadership #Transformation #Management

👉 The more people become proficient in living the Scrum values, the more successful the use of Scrum will be. Is there any impact of living (or not) the Scrum Values on the Artifacts...? And if so what would this impact possibly be...? The ScrumGuide states that each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured. For the Increment this commitment is the Definition of Done (DoD). This implies that the Scrum Team Commits to put their efforts in reaching the required quality level for the product, Sprint after Sprint. This will bring transparency to all stakeholders in that sense that they can count on it that the product has reached the quality levels as defined in the DoD. Openness and Respect will support bringing this transparency. Being open to share within the team if certain aspects of quality are not yet reached. Being open with the colleagues when shortcuts have been taken to reach the Sprint Goal, yet that can undermine quality in the longer run. Respecting that sometimes things do take longer in order to reach the needed quality levels for the Increment. Technical Debt will exist. Question is when the team needs to pay it back. Having the Courage to address technical debt so that the product's quality levels can be maintained in the future. It is probably not a lot of fun to deal with a legacy. Collect your courage and address it anyway. Just as the Sprint Goal is a Focus for the team, so is the quality. A Sprint Goal cannot be reached of the quality is not adequate. Focus on this team goal. These are only one example of how each Scrum Value supports delivering a better Increment. Summary: Using the Scrum Values as a guide for the Scrum Team how to behave during the entire Sprint will support raising transparency, which is the purpose of the Artifacts. For the Increment this means raising the transparency on the quality of the product. The expected quality goals are described in the Definition of Done. The more the team becomes skilled in living the Scrum Values, the more transparent the Increment will be. Prompt Together with your Scrum Team, evaluate how living the Scrum Values can still improve Increment Transparency. How do you see that the values of Commitment, Courage, Focus, Openness and Respect are lived? What can you do to make the Scrum Team live these even better? We hope you will find value in these short messages and if you are looking for more clarifications, feel free to take contact. Interested in more? Watch out for upcoming posts. Don't want to miss any of these posts? You can have them weekly in your mailbox via https://lnkd.in/dmyDEqm I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact. #Scrum #Simplification #BoostYourScrum

I experimented going into Agile adoptions not having formal Scrum Masters and Product Owners, check out how things turned out so far: https://lnkd.in/eRUJm8Sc

You should expect the use of Scrum to become more successful when the Team lives the Values of commitment, courage, focus, openness and respect. Then empiricism starts to work and trust is being built. 👉 The more people become proficient in living the Scrum values, the more successful the use of Scrum will be. Is there any impact of living (or not) the Scrum Values on the Artifacts...? And if so what would this impact possibly be...? The ScrumGuide states that each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured. For the Sprint Backlog this commitment is the Sprint Goal. This implies that the Scrum Team Commits to put their efforts in the Sprint Backlog so that all Developers have the same understanding when looking at the Sprint Backlog, and that this transparency allows them to measure progress towards the Sprint Goal. Openness and Respect will support bringing this transparency. Being open to understand the colleagues and respecting their experiences allows the team to identify the work that is really needed to reach the Sprint Goal. New work will be identified during the Sprint. Having the Courage to admit work was overlooked, and often could not have been identified earlier, allows to discuss the best way forward asap. Again, make these new insights transparant asap in the Sprint Backlog. The Sprint Goal, part of the Sprint Backlog, should be the Focus for the team. A razor-sharp focus on the Sprint Goal will ensure the team can deliver. Sprint after Sprint. These are only one example of how each Scrum Value is supported through a good use of the Sprint Backlog. Summary: Using the Scrum Values as a guide for the Scrum Team how to behave during the entire Sprint will support raising transparency, which is the purpose of the Artifacts. For the Sprint Backlog this means raising the transparency on what the Developers plan to accomplish during the Sprint to reach the Sprint Goal . The more the team becomes skilled in living the Scrum Values, the more transparent the Sprint Backlog will be. Prompt Together with your Scrum Team, evaluate how living the Scrum Values can still improve Sprint Backlog Transparency. How do you see that the values of Commitment, Courage, Focus, Openness and Respect are lived? What can you do to make the Scrum Team live these even better? We hope you will find value in these short messages and if you are looking for more clarifications, feel free to take contact. Interested in more? Watch out for upcoming posts. Don't want to miss any of these posts? You can have them weekly in your mailbox via https://lnkd.in/dmyDEqm I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact. #Scrum #Simplification #BoostYourScrum