Remove Cadence Remove Lean Remove Software Review Remove Underperforming Technical Team
article thumbnail

Beyond Mechanical Scrum

Scrum.org

The teams at his company had well established cadences for their Scrum events; well-oiled Daily Scrums that are done within 15 minutes and result in transparency of what the team will do for the next 24-hours. They are releasing software after every 2-week sprint. Welcome to Lean Startup. Kanban 101.

article thumbnail

Episode 189 – Harmonizing Potential – The Jazz of High-Performing Project Teams

Velociteach

Learn from the intriguing parallels between a jazz ensemble and an effective project team. Leonard demonstrates that music and project management share common principles as he offers a unique perspective on fostering a high-performing project team through the integration of music, productivity, workplace culture, and neuroscience.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The Difference Between The Kanban Method and Scrum

Digite

Continuing our theme of helping Agile teams understand the Kanban Method, so they can effectively adopt it for their improvement efforts, I am again honored to publish a guest article by another great friend of ours – Dave White. The Kanban Method pulls a great deal of its values from a Lean value system. Cheers, Mahesh Singh.

Cadence 94
article thumbnail

4 Common Misconceptions About Agile Transformation

Leading Agile

As a community, we have developed a handful of team-based Agile approaches over the years; some of which we would consider scaled. We have these small teams working on troubled projects. Eventually, they landed on the ideas of Test-Driven Development and Continuous Integration and Deployment. But here we are.

Agile 133
article thumbnail

Don’t Say NoGet Them to Understand Your Team Delivery Capacity

Leading Agile

Do you, or the teams you work with, feel pressure from stakeholders to say “yes” to everything they ask for? I often see advice from coaches that teams should learn to say “no” to stakeholders. I often see advice from coaches that teams should learn to say “no” to stakeholders.

article thumbnail

Creating a Risk-Adjusted Backlog

Leading Answers

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them. Prioritizing based on business value is an example of the lean concept of 'Taking an Economic View of Decision Making.' I do not think the teams have been weak at threat avoidance.

Risk 145
article thumbnail

Scrum or Kanban for Application Support teams?

Digite

The questioner asked – “I have recently joined a company and to one of the projects that I’m engaged we have this Scrum team that has a mixed backlog (USs and Bugs). This team’s goal is to be fixing urgent bugs and when they aren’t (doesn’t happen that often :)) they should work on the product increment.