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

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

According to the latest State of Agile survey from Digital.ai, 90% of teams who are using an Agile framework are using Scrum. For example, Scrum includes five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review and the Sprint Retrospective. Let the team decide what works best for them. That is the power of Scrum.

SCRUM 159
Insiders

Sign Up for our Newsletter

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

article thumbnail

Project Communication Management: What is it all about?

Rebel’s Guide to PM

Did you know that 56% of your project budget might be at risk due to poor communications? One of the most valuable resources in a project is the people (developers, engineers, subject matter experts, etc.) One of the most valuable resources in a project is the people (developers, engineers, subject matter experts, etc.)

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. Moreover, I added some food for thought.

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. . Nexus Integration Team (NIT) - System Team. Nexus - ART. Scrum Master in the NIT - RTE.

Cadence 132
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
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. But is having the roles, events and artifacts in place enough to make you “Agile”? Kanban 101.