Scrum.org

MARCH 18, 2019

I have been hiring Scrum Masters lately. So far, I hired 2 Scrum Masters whose answer to the question didn’t have any of those metrics. Rarely do you hear Scrum practitioners bringing up Cycle Time, Lead Time, Throughput, Work Item Age. Starting Our Agile Metrics Engines. Entering PSK. Because it is.

Agile 135

Agile Cadence SCRUM Software Review 135

Planio

JULY 4, 2022

Daily scrum ceremony. Sprint review ceremony. Agile ceremonies — also known as Scrum ceremonies or just ‘events’ — are specific events that provide a structured framework for iterative software development processes. Agile is an umbrella term for different iterative and feedback-driven software development processes.

Agile 88

Agile Technical Review Development Team Review Software Review 88

Scrum.org

MARCH 18, 2019

I have been hiring Scrum Masters lately. So far, I hired 2 Scrum Masters whose answer to the question didn’t have any of those metrics. Rarely do you hear Scrum practitioners bringing up Cycle Time, Lead Time, Throughput, Work Item Age. Starting Our Agile Metrics Engines. Entering PSK. Because it is.

Agile 98

Agile Cadence SCRUM Software Review 98

Digite

MAY 26, 2017

Program Increments (PIs) provide a development timebox (default 10 weeks) that uses cadence and synchronization to facilitate planning, limiting WIP, provide for aggregation of value and assure consistent retrospectives. In the case of IT and software domain, that would mean working- software). Release Train Engineer.

Agile 98

Agile Cadence Logistics Construction 98

Wrike

MAY 23, 2023

Agile methodology has emerged as a dominant approach to software development as it offers several advantages compared to traditional methods. Sprint Review is the ceremony where the team presents the completed work to the Product Owner and stakeholders for feedback. This way, the most important features are delivered first.

Agile 36

Agile Software Review Cadence Estimate 36

Leading Agile

AUGUST 13, 2018

Technical teams who are building or supporting application software usually work from a prioritized list of improvements, new features, and ideas to try out. Scrum calls the list the Product Backlog.) People leave and are replaced with new team members who don’t know the code base or the organization’s internal procedures.

Software Review 98

Software Review Technical Review Cadence SCRUM 98

Scrum.org

JANUARY 10, 2021

In my last post about Professional software teams creating working software David Corbin made a good point. Updated to reflect the 2020 Scrum Guide! TL;DR; Your Developers are ultimately responsible for creating done increments of working software. The 2020 Scrum Guide. Done Increments. So what do you do?

Software Review 232

Software Review Cadence Underperforming Technical Team 2020 232

Scrum.org

MARCH 11, 2024

This article covers the three Scrum accountabilities (formerly roles) and addresses interferences of stakeholders and IT/line management with this crucial Scrum event. Your single best investment to improve your professional standing ; order the Scrum Anti-Patterns Guide book now! ? Source : Scrum Guide 2020.

Technical Review 177

Technical Review Underperforming Technical Team Software Review SCRUM 177

Scrum.org

MARCH 28, 2022

Welcome to the Sprint anti-patterns article from my series on Scrum anti-patterns, covering the three Scrum roles—pardon me: accountabilities—and addressing the contributions of stakeholders and the IT/line management. Join Stefan in one of his upcoming Professional Scrum training classes ! Source : Scrum Guide 2020.

SCRUM 175

SCRUM Technical Review Software Review Consulting 175

Leading Agile

MAY 3, 2023

But as I’m sure a lot of you guys have seen as a lot of people run around doing Scrum or SAFe or whatever, and they’re not actually achieving the goals of agility and you know what’s hard? It happened with RUP, it happens with SAFe, it happens with Scrum, it happens with everything. Is there a product owner?

Agile 62

Agile Technical Review Governance Government 62

Scrum.org

JANUARY 10, 2021

Updated to reflect the 2020 Scrum Guide! TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software.

Software Review 230

Software Review Technical Review Planning Manufacturing 230

Leading Agile

MARCH 31, 2020

You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. The way I got into it was when I was at Perot systems, I was working in Jim champions organization and champion was one of the guys that led business process re-engineering. How do you like fix it? – Yeah. – Right.

Agile 71

Agile Technical Review SCRUM Engineering 71

Digite

MARCH 12, 2018

Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. In the usual Scrum process, the P.O. In my over 25+ years in the software industry, this has been an all too familiar situation! One column per person/pair?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

MPUG

JANUARY 31, 2022

Many times, managing a Hybrid-Agile project with a sole Lean-Agile approach doesn’t meet the needs of an organization, the expectations of stakeholders, required delivery frequency of customers, or address uncertainties associated with engineering work. I’ve derived the word ScrumBan by combining Scrum with Kanban.

Agile 111

Agile Software Review SCRUM Cadence 111

Redbooth

APRIL 26, 2018

The model has been favored by software engineers for its efficacy and flexibility, and it’s beginning to catch on in agencies and startups. Cut down work periods through sprints, daily standups, and reviews. Scrum Master : The player-coach most akin to a project manager who oversees operations and guards the process.

Agile 128

Agile Technical Review Software Review Cadence 128

MPUG

MAY 18, 2022

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. For those of you who are PMPs, your activity code today is on the screen. Lewis’ and James Mills JR.’s You may watch the recording of this webinar at your convenience.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Leading Agile

OCTOBER 3, 2023

When I first started thinking through this idea, I was actually really thinking about the idea of practices because back in 2010, a little bit earlier than that, Jim Kundiff, the Scrum Alliance, and those guys were really popularizing the CSM certification, PMI was doing the PMI ACP or a lot of us were part of that. So think about scrum.

Governance 62

Governance Government SCRUM Agile 62

Wrike

FEBRUARY 20, 2023

It is especially useful in software development and enterprise product management as these teams tackle projects and programs on extended timelines with continuous improvements, upgrades, and iterations released and delivered to customers over time. An example could be a fast-growing engineering firm with multiple departments and projects.

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Leading Agile

FEBRUARY 11, 2019

It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” Zombie Scrum describes the impact on delivery teams. Today, some of the same principles seem to present impediments or unnecessary challenges for many teams and organizations. What has changed?

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

Scrum.org

AUGUST 9, 2022

Business does not understand the complexity of software development or engineering work. Once you have a goal, it is crucial to measure the progress on cadence. Remember about cadences. Sprint Reviews. If you are a Product Owner or other Scrum Team member, you may use another opportunity to build.

Technical Review 186

Technical Review Cadence 2005 Initiating 186

MPUG

OCTOBER 16, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. And today’s session is eligible for one PMI PDU in the technical category, and the code for claim that is on the screen now, that’s mpugwebnlearn091819.

Agile 40

Agile Technical Review Software Review Engineering 40

Workamajig

JANUARY 11, 2021

Activity ID: An alphanumeric code used to identify an activity. The agile approach is usually used in software projects where the scope is not always known and adaptability is prioritized. Projects might additional calendars as well to show resource availability, communication cadence, etc.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Scrum.org

SEPTEMBER 19, 2020

Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. Scrum Events. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. TL; DR: 11 Proven Stakeholder Communication Tactics.

Technical Review 201

Technical Review Software Review Development Team Review Cadence 201