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

Unleashing Agile: Empowering Agile Teams for Managers

Leading Agile

Empowering your teams isn’t about allowing them to make decisions in a vacuum and giving them free rein to do whatever they want. The days of providing a little guidance here, some methodology there, and letting the teams self-organize their way to success are behind us. What does it mean to empower teams?

Agile 62
article thumbnail

Transformation, Business Architecture, and Scaling

Leading Agile

More often than not in kind of either the IT product development space or IT services space. We like to consider ourselves kind of a full stack consultancy in the sense that you know, obviously, you have to deal with the work surface levels and what the teams are doing but you know, how do you orchestrate teams across dependency boundaries?

Agile 140
Insiders

Sign Up for our Newsletter

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

article thumbnail

Sprint Anti-Patterns

Scrum.org

TL; DR: Sprint Anti-Patterns Holding Your Teams Back Welcome to Sprint anti-patterns! This article covers the three Scrum accountabilities (formerly roles) and addresses interferences of stakeholders and IT/line management with this crucial Scrum event. Join Stefan in one of his upcoming Professional Scrum training classes !

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

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. Scrum focuses more on management activities.

Agile 131
article thumbnail

Dealing With “Remote Sprawl”: How to Manage Teams, People, and Projects Across Time Zones

Planio

It’s quickly becoming the ‘new normal’ for companies and teams to be split across cities, countries, and even time zones. And while there’s no denying the many benefits of working remotely , mismatched schedules, repetitive communication, and out-of-sync teams don’t make the list. Poor people management: Embrace your team’s nuances.

article thumbnail

How I transformed “multiple Scrum teams” into “multiple team Scrum”

Scrum.org

Intended audience: Scrum masters, Product owners, Managers and Agile coaches. The PO’s are then unsure what needs to be developed. For instance, a lead developer or architect prepares the work for sprints ahead, acting as a proxy between the teams and the PO’s, splitting the requirements in tasks per team.