As organizations strive to scale their agile practices, the Large Scale Scrum (LeSS) framework provides a streamlined solution. By promoting simplicity, transparency, and cross-functional teamwork, LeSS helps teams collaborate effectively while maintaining the core principles of Scrum. This post explores the key concepts, benefits, and challenges of implementing LeSS, along with resources for further learning.
In today’s fast-paced software development landscape, efficiency is key to staying ahead. Discover how continuous delivery revolutionizes workflows, empowering teams to deploy updates swiftly and reliably. Embrace the power of CD and transform your development process.
The answer to that question according to the Scrum Alliance is: An agile coach helps individuals, teams, and entire enterprises embrace a culture shift based on proven human-centric agile principles, practices, and values. This culture shift helps people and organizations continue to thrive in the ever-changing world of work. That sounds good to me, so let’s dig a bit deeper into what is the actual work that an agile coach does in order to help individuals, teams and entire enterprises. Does an agile coach actually coach? To answer that you need to find out what it actually takes to embrace a culture shift based on proven human-centric agile principles, practices, and values. Obviously an agile coach needs to convey values …
Measuring and using velocity of an agile team can be helpful in forecasting output of the near future. You need a certain stability in your team and enough data points / iterations. However, there are also things that could go wrong using velocity. Therefore I want to shed some light on pitfalls using velocity in agile planning. Velocity is not a measure for productivity! Velocity is only an indicator of how much work was done in the past, not how much work will be done in the future. It’s like measuring your running speed with a stopwatch and then using this value to predict how fast you can run tomorrow or next week. We would be able to predict who will …
In product development there is a lot of focus on the value creating units, the teams. As many products are developed in a complex context with a certain degree of uncertainty, teams should apply emergent development practices. Teams also should make decision out of their context rather than developing a product based decisions they didn’t make or where not involved in. Teams already get good support in order to do so by adding roles like Scrum Masters or Agile Coaches. What is often forgotten about, is to also adapt the environment that the team is working in. The consequence is that, once teams reach a certain maturity regarding emergent and self-organized way of working, conflicts with regards to the team’s …