Digite

MAY 15, 2018

This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

MPUG

DECEMBER 28, 2020

A new version of Scrum guide was released last month. It contains commitments for each of the Scrum artifacts. The Product Owner (PO) is the person who is responsible in building, and clearly communicating product goal to the team. Product Goal also reflects one of the values of Scrum: “Focus.” Commitment based Artifacts.

Cadence 116

Cadence SCRUM 2020 Agile 116

nTask

OCTOBER 5, 2021

Compared to other methodologies out there like scrum , this methodology might seem unpredictable or unorganized due to its flexibility, but in reality, the Kanban project management methodology operates in certain choreographed rhythms. What are Kanban Cadences? 7 Different Kanban Cadences Meeting Types.

Cadence 78

Cadence 2021 Development Team Review Risk Management 78

Scrum.org

OCTOBER 2, 2018

If you’re also an experienced Scrum practitioner, you probably associate the time you started to use Scrum with the time you started to release more frequently. Transcending Scrum and the Sprint Increment? Before you recycle your copies of the Scrum Guide – can I ask you a couple of questions though?

Cadence 141

Cadence Development Team Review Technical Review Software Review 141

Scrum.org

OCTOBER 2, 2018

If you’re also an experienced Scrum practitioner, you probably associate the time you started to use Scrum with the time you started to release more frequently. Transcending Scrum and the Increment? Before you recycle your copies of the Scrum Guide – can I ask you a couple of questions though? You were pretty proud.

Cadence 140

Cadence Development Team Review Technical Review Software Review 140

Digite

FEBRUARY 13, 2018

In this article, he outlines the similarities of the two as WIP Limiting, Pull-based systems – with cadences and a focus on learning – while also explaining their differences. A question that I often get while speaking with people is: What is the difference between Kanban and Scrum? You will enjoy this excellent article.

SCRUM 94

SCRUM Cadence Lean Underperforming Technical Team 94

Scrum.org

JANUARY 10, 2021

Updated to reflect the 2020 Scrum Guide! Any software that you create is an organisational asset and decisions to cut quality need to be reflected in your company accounts and as such those decisions need to made by your executive leadership and should not be made by Developers. Professional Developers create working software.

Software Review 230

Software Review Technical Review Planning Manufacturing 230

Scrum.org

MARCH 14, 2023

After focusing, delivering goes – as a shift towards creating customer-facing self-managing teams. In Scrum terms, this is about improving upon the Definition of Done. And in the 21st century for software development teams, this means realizing the paradigm of Continuous Delivery. Not to get stuck in mediocrity.

Agile 225

Agile Cadence Technical Review Development Team Review 225

Scrum.org

JANUARY 14, 2021

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. . Scrum theory emphasizes Empiricism and Self-management, coupled with Flow in recent years.

Cadence 107

Cadence Technical Review Development Team Review Lean 107

Scrum.org

NOVEMBER 18, 2020

With the release of the 2020 version of the Scrum Guide, we now have Product Goals but what are they? See the Professional Scrum Product Owner book for more details. Development teams and stakeholders can “see” how they connect. Try aligning your Product Goals with quarterly business reviews. Product Samurai.

2009 234

2009 Underperforming Technical Team Cadence SCRUM 234

Leading Answers

NOVEMBER 1, 2020

Instead, the team regularly surfaces from work to show where they are with progress and discuss what should come next. It is this predictable cadence of show-and-tell sessions that creates the dolphins-versus-submarines comparison.  It facilitates collaboration, load-sharing and team planning.

Agile 135

Agile Planning Underperforming Technical Team Development Team Review 135

Agilemania

NOVEMBER 30, 2021

Planning and Execution of Program Increment: A SAFe Agilist has envisioned a roadmap for the success of the Agile Development and successful SAFe implementation process. They start strategic planning as a lead which sets the plan for the Development team to realize the goal of becoming an Agile organization. Author's Bio.

Cadence 98

Cadence Lean 2011 Agile 98

Agilemania

SEPTEMBER 15, 2022

Your team is granted funds that are decided by strategic needs, and they make sure your goals align with those needs. In order to connect strategy to execution The leadership team evaluates these targets on a regular basis. “Go see” the incremental value demonstrated in team demos and validate the value hypotheses.

Lean 98

Lean Cadence Development Team Review Leadership 98

Leading Agile

JULY 28, 2022

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. They can negotiate the amount of work they accept into their sprint during sprint planning based on their team’s past velocity.

Agile 127

Agile Technical Review Cadence Software Review 127

Digite

JUNE 13, 2018

Compared to Scrum, Kanban is a young work-management method. Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development.

Agile 110

Agile Technical Review Cadence Software Review 110

MPUG

SEPTEMBER 4, 2023

The style of project management The organization may have a preferred methodology or paradigm, and the project manager (along with their team) will also assess what is right for this project. However, to illustrate with Scrum, let’s consider the Sprint Reviews and Sprint Retrospectives of Scrum.

Risk Management 98

Risk Management Risk Agile Technical Review 98

Planio

NOVEMBER 11, 2020

The official Scrum Guide describes a sprint retrospective as: A meeting held at the end of a sprint where the Scrum Team can inspect itself and create a plan for future improvements to systems, processes, and workflows. Agile project development is all about continuous improvement. What is a sprint retrospective?

Underperforming Technical Team 135

Underperforming Technical Team Development Team Review SCRUM Agile 135

Teamweek

APRIL 29, 2020

Right now, project managers are falling in love with Scrum and Kanban boards. If you need a way to schedule your tasks and teams, either or both of these frameworks will do the trick. Whether you are working on your own from home or have a large team to manage, these boards will help you schedule your work as efficiently as possible.

SCRUM 59

SCRUM Cadence Software Review Development Team Review 59

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. Daily scrum ceremony. Sprint review ceremony. Daily scrum (or daily stand-up): These daily check-ups help teams stay on track and mark progress.

Agile 88

Agile Technical Review Development Team Review Software Review 88

Project Pulse Journal

APRIL 8, 2024

This domain facilitates strategic alignment, optimized delivery cadence, methodology customization, increased flexibility, and improved risk management. The desire for a project management framework that sustains deliverability, supports the required cadence, and remains faithful to an adaptable methodology is now within reach.

Underperforming Technical Team 52

Underperforming Technical Team Cadence Development Team Review Technical Review 52

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

International Institute for Learning

APRIL 19, 2023

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. They offer practitioners tools to extend and mature their agility beyond the team to programs and the broader enterprise. To coordinate the teams, SAFe applies cadence and synchronization. This configuration creates a balance of power.

Agile 59

Agile Cadence Certification Lean 59

Wrike

SEPTEMBER 25, 2023

Safe Scrum is a framework that has gained significant popularity in recent years for enhancing team performance in an agile development methodology. By providing clear guidelines and principles, Safe Scrum enables teams to collaborate more effectively, communicate transparently, and ultimately deliver higher-quality projects.

SCRUM 36

SCRUM Cadence Development Team Review Software Review 36

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. But a full Agile transformation isn’t just about the development process you use — it’s a way to bring creativity, innovation, and lean operations to every aspect of your business. This is ok.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Leading Agile

AUGUST 19, 2020

They did a great job of getting the message out Scrum and the Scrum certification did a great job of getting the message out. Does it mean that we start Doing Scrum, right? Those are the things that get in the way of making Scrum not work in a lot of organizations. So we’re going to put a team here, right?

Agile 100

Agile SCRUM Governance Government 100

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. Think of your favorite mobile apps (e.g., What are the principles of SAFe?

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

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 2003 Governance 42

Leading Agile

MARCH 17, 2021

And then how do we make decisions when teams are in conflict and how do we subordinate backlogs to a portfolio? If you just do Scrum, you’ll get the goodness out of it. I don’t mean Scrum. And so I did talk on the three things and then we came up with this talk. It was just why agile fails. How do we control things?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

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

10 years ago, it seemed that a little Scrum here and some coaching there would suffice. Different change cadences. The package is changing at one cadence and maybe you’re trying to innovate and change at another cadence, right? You need to be able to upgrade one without having to involve all the other teams.

Fractional CTO 126

Fractional CTO Software Review Technical Review Agile 126

Scrum.org

SEPTEMBER 19, 2020

Run a quick mental exercise: Try walking in your stakeholders’ shoes, and ask yourself: Would you entrust your career a bunch of hoodie-wearing nerds, promising a big reward because they are practicing XP and Scrum? Scrum Events. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team.

Technical Review 232

Technical Review Software Review Development Team Review Cadence 232

Agilemania

MAY 17, 2021

The organizations start with few teams initially, and it is easier to follow simple & lightweight frameworks like Scrum or Kanban at this stage. As businesses grow, more and more teams start adopting agile. These challenges make it difficult in: Managing inter-team dependencies to deliver an Increment. Scrum@Scale.

Agile 98

Agile Lean SCRUM Cadence 98

Agilemania

MAY 17, 2021

The organizations start with few teams initially, and it is easier to follow simple & lightweight frameworks like Scrum or Kanban at this stage. As businesses grow, more and more teams start adopting agile. These challenges make it difficult in: Managing inter-team dependencies to deliver an Increment. Scrum@Scale.

Agile 84

Agile Lean SCRUM Cadence 84

Velociteach

MAY 10, 2023

Pioneering software development thought leaders collaborated to create the Manifesto (2001). The Manifesto distills concepts from eXtremee Programming , Scrum, and other leading development practices. Customers and development teams should work together daily. Scrum Scrum is the most widely used Agile framework.

Lean 89

Lean Cadence PMI 2001 89

Scrum.org

AUGUST 24, 2020

The Scrum Master tactics series are a series of articles in which I write about and explore contemporary techniques that will aid you in your journey as a Scrum Master. The tactics explained stem from my personal experience as a Scrum Master which I accumulated over the years in working with many different teams and contexts.

SCRUM 229

SCRUM Development Team Review Cadence Initiating 229