This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
One of the biggest reasons agile fails to take root inside these organizations is resistance or hesitation from their executive teams. Their hesitation toward Agile often comes from a place of caution, rooted in a preference for traditional methods that provide clear metrics and established processes.
We had a fortnightly release (and therefore a giant scrabble to try to get your changes in before the cut-off and presented to the CAB in time), but your company might have monthly releases or use a different cadence. It’s no longer necessary for agile teams to be co-located, either. How to become a release manager.
The concept of self-managing teams is not just a characteristic of Scrum; it is one of the foundational principles of the Agile Manifesto, where the term “self-organizing teams” is used (note that discussing similarities and differences between self-organising and self-managing is an unnecessary detour in the context of this article).
We cover how to create these scatter plots in the Applying Flow Metrics for Scrum and Professional Scrum with Kanban classes. Armed with the data, you can set realistic deadlines, allocate resources efficiently, and prevent delays that might disrupt your delivery cadence. Contact us today to begin your journey.
This is challenging but satisfying (TIP: Slicing outcomes is similar to identifying a Minimum Viable Product, Minimally marketable features, and Slicing Stories… so your Product leaders and Agile practitioners can help out on this front). Figuring out the right Cadence . Disconnect/confusion between OKRs and agile ways of working.
TL; DR: Agile Transformation with ChatGPT or McBoston? I was interested in learning more about a typical daily challenge many agile practitioners face: How shall we successfully pursue an agile transformation? Or shall we embark on an agile transformation with ChatGPT providing some guidance?
I proposed the Daily Scrum Meeting, along with two other activities , as an Agile practice you can adopt if you want to gain some of the benefits of Agile – even if your team hasn’t adopted full Agile. Agile takes discipline. By meeting at the same time, your team gets into a regular cadence.
The specific cadence varies based on the complexity and duration of a transformation. This is why regardless of the nature of a transformation we need to inject agility into its delivery. At regular intervals, the team reflects on how to implement change more effectively , then tunes and adjusts its behavior accordingly.
User Training and Documentation Sprint Goal - "By the end of this sprint, we will have provided training to all relevant stakeholders on how to use the migrated applications in the cloud environment and created comprehensive documentation." Create a Cadence of Accountability. Act on Lead Measures. Keep a Compelling Scoreboard.
I don’t spend a bunch of time on LinkedIn, but the other day, I was scrolling around and happened to catch a thread where some folks in the Agile community were debating if SAFe was actually Agile. The post generated a lot of good conversation, so I thought I’d take a minute and share how I think about this. What is Agile?
I was hired by a bank to help them to get started with agile and Scrum. I took the opportunity to present myself as the Agile Coach facilitating the change and explained in a couple of words the essence of working with Scrum. The goal was to synchronize the three teams so that they all got into the same cadence. Introduction.
I was hired by a bank to help them to get started with agile and Scrum. I took the opportunity to present myself as the Agile Coach facilitating the change and explained in a couple of words the essence of working with Scrum. The goal was to synchronize the three teams so that they all got into the same cadence. Introduction.
The topic of Agile Metrics inevitably comes up in many situations and conversations. I cannot tell you how many candidates mention Velocity, Burndown and Burnup charts. Those numbers that matter, the Agile Metrics. Starting Our Agile Metrics Engines. I have been hiring Scrum Masters lately.
The book “ The Lean-Agile Way – Unleash Business Results in the Digital Era with Value Stream Management ” by Cecil ‘Gary’ Rupp, Richard Knaster, Steve Pereira, and Al Shalloway provides a comprehensive roadmap to optimize processes, improve products, and enhance service delivery.
An Agile Transformation Roadmap is all about getting people to change and having that change be sticky. It’s that they can’t see how to do it. It’s that they can’t see how to do it. They can’t see how to get from point A to point B safely and pragmatically. The Agile Transformation Steps.
Organizations look to Agile to overcome challenges. Many organizations struggle in their implementation of Agile and/or their evolution of agile once they start their journey. In the beginning, they have trouble seeing how it will work in their current day to day environment. What do Agile leaders do?
If those worlds are not connected, then there’s a limit to the level of business agility the IT department can support. Business agility is what organizations are looking for; agile software development may be one enabling factor in achieving it, but it isn’t the point of a transformation. Half-Agile Transformations.
So, there are no directions about HOW to run your Scrum team. The duration of the Sprint is timeboxed to a maximum of one month, establishing a cadence within which the Scrum team works together to deliver value. This is the best class for managers or supervisors of individuals who work on Agile or Scrum teams. . Conclusion.
Scaled Agile Framework, SAFe® is the world’s leading framework for Business Agility. The seven core competencies each have three dimensions making it a total of twenty-one dimensions to enable Business Agility. These dimensions contain some of the practices, patterns, and guidelines to Scale Agility across the enterprise.
SAFe includes Scrum - so how come many Scrum practitioners and thought leaders consider it unsafe? The Scaled Agile Framework (SAFe™) is one of the most popular approaches to applying agile at scale out there. In SAFe's Program Level, a key piece is the Agile Release Train which is considered a team of Agile teams.
As a community, we have developed a handful of team-based Agile approaches over the years; some of which we would consider scaled. Implementing Agile, especially in larger, more complex organizations, still seems to be a black art. All the things we consider hallmarks of a small team, Agile methodology. But here we are.
They cover the concept of the Product Owner role, product discovery, how to deal with external and internal stakeholders, product portfolio and product roadmap planning, and the Product Backlog refinement. The Product Owner can explain to any stakeholders how their requirements fit into the plan of how to achieve the product vision.
My perspective is based on my analysis, my own interpretations, and the interactions I’ve had with Agile practitioners who follow my publications, books, and/or courses. Introduction of Cadence. For the first time, we are introduced of a concept called “Cadence.” Product Goal. Lean Thinking.
Professional Scrum with User Experience: Gaining the Competitive Edge Discover how Professional Scrum with User Experience Training offers your team a competitive edge through a synergistic approach that enhances product success.
Agile needs to be tied to business-driven results. If not, then we start measuring things like people trained, teams doing Scrum, or the organization’s sentiment toward Agile to tell us if we’re succeeding. If your Agile isn’t helping you do that, then it’s not really Agile at all. First, how are we forming teams?
Many teams that operate within Agile are struggling. We find that the backlogs that Agile teams frequently operate from appear as a thematic list of items that the product owner wants built. How to Overcome the Difficulties of Building Backlogs in This Way.
If you work in tech or any industry where things change fast, you probably are familiar with agile project management. Agile methods are baked into productivity tech, from Trello to Airtable to Redbooth, and can improve any large body of work, from ad campaigns to app design. Agile project management basics: project as product.
Every day organisations are starting and failing with business agility, praise and blame Scrum. They are accountable for delivering done working products every cadence and satisfy customer needs. Professionals can plan how to perform their work best, accept the success or failure and adapt if needed. So what is the difference?
The goal of adopting Agile is always about achieving the desired business outcome unique to the organization that is pursuing it. The Agile mindset can be adapted to fit many industries or businesses. This means they know the scope of what’s required, how to complete it, and when it needs to be delivered.
When asked what an Agile organization is, most people tend to think it’s one that’s built around a certain mindset, or around Agile practices like Scrum or SAFe—or both. But if it were as simple as a mindset or process change, so many Agile Transformations wouldn’t fail. Base Patterns and Tools. Structure. ??Your
I think of the Sprint as the heartbeat of Scrum because it sets the cadence and frequency for the other events. Sprint Planning includes selecting what Product Backlog items (PBIs) to deliver and creating a plan for how to complete the work. How the Sprint Planning event reduces the need for other meetings. For Product Owners .
Dependencies will stop Agility dead in its tracks. In the presence of dependencies, you’re never going to achieve the level of Agility you desire—unless you do something about them. Theoretically, you could have two teams that meet most of the criteria of an Agile team. And that limits our ability to be Agile.
At a recent training class one of the delegates spoke about their present company, about how it was the most “Agile” place he had ever worked. Why then after the first day of training with us would he comment “I realise now that we are not Agile at all!”? Without the Agile mindset, Scrum just adds unnecessary overhead.
Some Agile experts are not hard-core fans of SAFe. And this makes SAFe more complicated, bureaucratic than the Agile manifesto recommends. They also have this opinion that SAFe is so heavy, maybe it is not Agile at all. Most of us started our Agile journey with one framework, and that is Scrum. Let us dig deeper.
Here’s everything I’ve learned about how to help remote teams collaborate and communicate effectively, openly, and honestly. How does it help teams collaborate? This is also closely related to the Agile idea of being a servant leader. Flat hierarchy: Agile promotes self-organizing teams. What is psychological safety?
When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. A lot of people see the Scrum Sprint as mainly a release cadence. The Scrum Sprint is first and foremost a Planning, Transparency, Inspection and Adaptation cadence.
Agile development and product development are aligned with business strategy through LPM, driving value to customers with products and solutions. Business agility can be improved by combining LPM and agile development practices. The leadership team facilitates periodic reviews to achieve enterprise agility: 1.
In addition to Fitness and Nutrition Coaching, I’m fortunate to serve two incredible teams as their Scrum Master and Agile Coach at a Fortune 100 company. The more I dove into learning about Scrum and its practices while I prepared for the Scrum Master role, the more I noticed similarities to how I approached my coaching practice.
Many organisations wrestle with the seeming incompatibility between agile and release management, and they struggle with release planning and predictable delivery. Without a regular cadence of delivery of working software any belief that you will get a usable increment is misguided at best. Updated to reflect the 2020 Scrum Guide!
Sprint Planning is a core event, defining how your customers’ lives will improve with the next Product Increment. Learn more on how to improve its effectiveness by avoiding 20 common Sprint Planning anti-patterns. The Development Team planning part is also well-suited to consider how to reduce technical debt, see above.).
When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. A lot of people see the Scrum Sprint as mainly a release cadence. The Scrum Sprint is first and foremost a Planning, Transparency, Inspection and Adaptation cadence.
So if we agree that Agile Transformation is worth talking about, we need a better way of talking about it. You see, over the past 20 years, the general hypothesis has been to train people on Agile methodologies and trust everything else will emerge. Once we understand where we are going, we can start to talk about how to get there.
The Agile Fluency model, developed by Diana Larsen and James Shore in 2012 and substantially updated in 2018, is a framework to help teams understand their current position and to help them develop an individual road map. Agile teams pass through four distinct zones of fluency as they learn ( fluency evolves).
When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” Stable Team. Dedicated Team. Team Spaces.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content