article thumbnail

The Agile Fluency Model with Diana Larsen

Scrum.org

After a short introduction to the model, we shifted to an ask-me-anything-style discussion of the groundbreaking view of agile and teams. ?? Quote: Focusing teams produce business value. Delivering teams deliver on the market cadence. Optimizing teams lead their market. Do zones always follow each other?

Agile 185
article thumbnail

Is SAFe Agile?

Leading Agile

It doesn’t mean they are bad. Agile is an incremental and iterative approach for developing software products. It’s typically best for small teams. The most common small team Agile methodologies are Scrum and XP, maybe Kanban, or a combination of the three. Kanban focuses more on flow and less on teams and time-boxes.

Agile 127
Insiders

Sign Up for our Newsletter

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

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

How to build psychological safety on remote teams

Planio

And that’s a problem — especially on remote teams. 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? Why it’s so hard to build psychological safety on remote teams. Set ground rules for how teams interact.

article thumbnail

Sprint Anti-Patterns

Scrum.org

TL; DR: Sprint Anti-Patterns Holding Your Teams Back Welcome to Sprint anti-patterns! Your single best investment to improve your professional standing ; order the Scrum Anti-Patterns Guide book now! ? However, once it moves from one backlog to the other, the Developers become responsible. And if so, what are the consequences?

article thumbnail

Event Series: Practical Kanban with MS Project Agile

MPUG

The team pulls a feature or work item from the backlog based on the available capacity, executes the work, and when complete, delivers the work incrementally. The delivery is based on a cadence. In each delivery, we have analysis, design, development, testing, and so on. The emphasis in Kanban is primarily on the flow of work.

Agile 52
article thumbnail

Product Goal

Scrum.org

Well, they are not new, lets take a trip down memory lane to the year 2009 and the book “The Toyota Kata” by Mike Rother. . See the Professional Scrum Product Owner book for more details. Development teams and stakeholders can “see” how they connect. Product Samurai. The diagram I scribbled below may help to explain.

2009 230