Scrum.org

JANUARY 10, 2021

Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Without a regular cadence of delivery of working software any belief that you will get a usable increment is misguided at best. Professional Developers create working software.

Software Review 230

Software Review Technical Review Planning Manufacturing 230

Scrum.org

NOVEMBER 18, 2020

Make at least one definitive move toward your goal.”?—?Bruce Development teams and stakeholders can “see” how they connect. Try aligning your Product Goals with quarterly business reviews. Product Goals are an often overlooked mechanism that can help you in this area. “If SMART , IVEST , whatever is your favorite.

2009 234

2009 Underperforming Technical Team Cadence SCRUM 234

MPUG

DECEMBER 28, 2020

This definition of the ‘goal’ can create confusion for many who understand project-program-portfolio management and how goals aligns with the vision, mission, strategy, and objectives of an organization. For Increment, the commitment is the Definition of Done (DoD). Introduction of Cadence. Lean Thinking.

Cadence 116

Cadence SCRUM 2020 Agile 116

Scrum.org

JANUARY 14, 2021

Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. The Nexus Sprint Review and the System Demo are similar events happening on a similar cadence - every several weeks (Sprint/Iteration). No team-level Sprint Review.

Cadence 107

Cadence Technical Review Development Team Review Lean 107

Leading Agile

JULY 28, 2022

They are the ones that must define clear acceptance criteria and definition of done. From a process perspective, like in Scrum, the product owner brings the backlog to the Scrum team, and they accept the work into their sprint. Getting to a Definition of Done. Avoid Pushing Work to the Next Sprint.

Agile 127

Agile Technical Review Cadence Software Review 127

Velociteach

MAY 10, 2023

Understanding the definitions is helpful: Principles define the fundamental beliefs that guide decision-making and behaviors. Iterative and incremental delivery, welcoming change, empowered teams, and regular customer engagement are some of its core practices. Customers and development teams should work together daily.

Lean 89

Lean Cadence PMI 2001 89

NimbleWork

APRIL 25, 2025

Reframing SWOT: Beyond Strategy, Into Execution SWOT analysis, Strengths, Weaknesses, Opportunities, and Threats, is often misunderstood as a high-level planning tool reserved for annual reviews or executive offsites. The legal teams new template may reduce review time ( opportunity ). tight handoffs between design and dev).

Underperforming Technical Team 78

Underperforming Technical Team Development Team Review Cadence Risk Management 78

Agilemania

MAY 17, 2021

Agile coaches help train development teams, product owners, executives on the agile methodology and oversee the development of agile teams to ensure effective outcomes for the organization. S/He leads implementation workshops (value stream identification/mapping, identification of ARTs, the definition of EPIC, etc.)

Agile 98

Agile Lean SCRUM Cadence 98

Digite

JUNE 13, 2018

For example, your team of 5 might have a WIP limit of 10 on their “Doing” column, enabling each person to work on 2 things at once. The limit on work being reviewed, however, might be different, depending on how long this piece of the workflow takes, how many people are assigned to review work, and other factors.

Agile 110

Agile Technical Review Cadence Software Review 110

Agilemania

DECEMBER 2, 2021

Apply cadence and synchronize with cross-domain planning. Long term planning and iterations for big teams. The first challenge faced by Agile teams that tops the list is planning ahead and carrying out iterations for big teams. Development teams work seamlessly in purifying their iterations.

Technical Review 98

Technical Review Agile Software Review Lean 98

Agilemania

MAY 17, 2021

Agile coaches help train development teams, product owners, executives on the agile methodology and oversee the development of agile teams to ensure effective outcomes for the organization. S/He leads implementation workshops (value stream identification/mapping, identification of ARTs, the definition of EPIC, etc.)

Agile 84

Agile Lean SCRUM Cadence 84

Planio

JULY 4, 2022

Agile ceremonies are the fuel that keeps your development team moving forward. Agile ceremonies get abandoned when teams stop seeing the value in them. (And Sprint review ceremony. Each morning, team members discuss what they worked on yesterday, what they’re doing today, and what’s blocking them from moving forward.

Agile 88

Agile Technical Review Development Team Review Software Review 88

Planio

AUGUST 9, 2021

You’ll need to collaborate with product managers, team leads, stakeholders, and the development team to make sure everyone agrees on the timeline. Set a deadline for when you need to meet your definition of done and launch the project. But Agile teams also need to stay on track. Why the project manager?

Software Review 78

Software Review Technical Review Estimate Agile 78

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. You’re going to see this coming out at a very fast cadence. Tim Runcie: So I might just say, urgent review right? Add a bucket.

Agile 40

Agile Technical Review Software Review Engineering 40

Leading Agile

JULY 3, 2023

Different change cadences. The package is changing at one cadence and maybe you’re trying to innovate and change at another cadence, right? You want to be able to mark things that aren’t available because now you can move the package, something moving at different cadences. Also, review performance measures.

Software Review 126

Software Review Fractional CTO Technical Review Agile 126

Scrum.org

OCTOBER 2, 2018

When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. The role of the Sprint.

Cadence 156

Cadence Development Team Review Technical Review Software Review 156

Scrum.org

OCTOBER 2, 2018

When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. The role of the Sprint.

Cadence 150

Cadence Development Team Review Technical Review Software Review 150

Leading Agile

AUGUST 19, 2020

They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right? Why is acceptance criteria or definition of done or deployability or even so far as to extend it out to like we actually have deployed it with customer? They pull a chunk off the backlog. Why is that important?

Agile 98

Agile SCRUM Governance Government 98

Herding Cats

APRIL 16, 2019

The following material comes from conferences, workshop, materials developed for clients. The overarching theme is focused on defining what Done looks like, assessing progress toward Done in units of measure meaningful to the decision makers. Project Success Assessment - A checklist for assessing the processes for project success.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team 2003 42

Leading Agile

MARCH 17, 2021

They do daily stand-ups, they do reviews and retrospectives. And then you can imagine an in-state where you have encapsulated value streams, really solid business ownership, value streams are able to produce small batches on a regular cadence, and the capabilities are largely grouped, the ones that work together.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Leading Agile

AUGUST 20, 2018

Reviewing code by eyeballing it to ensure compliance with coding standards. An unattended CI/CD pipeline has to satisfy the needs of all stakeholders without requiring a halt for manual review and approval. As a general rule, anything that requires a halt and manual review is probably designed in a suboptimal way.

Software Review 75

Software Review Software Technical Review Development Team Review 75