Remove Cadence Remove Lean Remove SCRUM Remove Underperforming Technical Team
article thumbnail

Scrum: 20 Sprint Planning Anti-Patterns

Scrum.org

TL; DR: Scrum Master Anti-Patterns. Join Stefan in one of his upcoming Professional Scrum training classes ! Scrum’s Sprint Planning aims to align the Developers and the Product Owner on what to build next, delivering the highest possible value to customers. Shall I notify you about articles like this one?

SCRUM 195
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. The Scrum Guide is explicit in stating that Scrum is a framework. Welcome to Lean Startup.

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. A question that I often get while speaking with people is: What is the difference between Kanban and Scrum?

Cadence 94
article thumbnail

Comparing Nexus and SAFe - Similarities, Differences, potential synergies

Scrum.org

The Nexus group of teams is very similar to the Agile Release Train (ART) construct. In both SAFe/Scrum it is a self-managing team of self-managed teams with a couple of key roles at the team of teams level. . Scrum theory emphasizes Empiricism and Self-management, coupled with Flow in recent years.

Cadence 137
article thumbnail

Event Series: Practical Kanban with MS Project Agile

MPUG

Two widely accepted Lean-Agile approaches, iteration- and flow-based, are embraced by Agile practitioners. The most well-known framework for iteration-based Agile is Scrum , while Kanban represents flow-based Agile. The delivery is based on a cadence. In each delivery, we have analysis, design, development, testing, and so on.

Agile 52
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.

article thumbnail

Agile Communications Plans

Leading Answers

Demos  – Having the team demonstrate increments of functionality at the end of every iteration shows what the project has achieved to date. Instead, the team regularly surfaces from work to show where they are with progress and discuss what should come next. Information radiators can show any data the team wants to display.

Agile 135