Scrum.org

MARCH 14, 2023

In Scrum terms, this is about improving upon the Definition of Done. Plus, the technical capabilities in the form of teams focused on the value as goals and priorities. We have reviewed those ideas in an article on Team Topologies and highlighted some serious drawbacks of such an org design. A good example here would be SAFe.

Agile 220

Agile Cadence Technical Review Development Team Review 220

Inloox

JULY 1, 2021

In most cases, however, previous experience is based only on the small-scale use of Scrum or other agile methods in individual departments. Large corporations in particular, which are in urgent need of more agility due to entrenched structures, usually have the hardest time implementing an agile transformation. But it’s not that easy.

Technical Review 100

Technical Review Lean 2011 Cadence 100

Scrum.org

OCTOBER 6, 2019

In the world of tech, many industry giants such as Google choose to use a management framework known as Objectives and Key Results (OKR). This role is very similar to that of a Scrum Master. A Scrum Master may decide to take on the role of OKR Champion as part of a servant leadership commitment to the organization and Scrum Team.

Technical Review 154

Technical Review Cadence Information Technology Defining 154

Scrum.org

MAY 14, 2020

Technology alone won’t solve the problem. We are Scrum practitioners. And Scrum is an Agile framework that organises teams using five events, three roles and three artefacts. . Skilful use of the Scrum framework creates environments biased toward action and optimised for transparency, learning and adaptation.

Agile 195

Agile Technical Review Software Review Cadence 195

Scrum.org

MAY 27, 2021

The following five simple events derived from Scrum offer leaders and managers a way of regularly checking-in with their teams, always being present for them without falling into the pitfalls of micro-management. These five events from Scrum strongly support a decentralised command approach. #1 4 – The Review. 1 – Planning.

Agile 248

Agile Cadence Technical Review Software Review 248

MPUG

SEPTEMBER 4, 2023

What agile adds to this, therefore, is a distinct cadence of its own iterations or drawdowns of tasks into the Work in Progress part of the Kanban Board. Rapid changes in the market demand arising from social trends, competitor activities, or technical capability, for example. Rapid development in the technology available.

Risk Management 98

Risk Management Risk Agile Technical Review 98

Leading Agile

APRIL 24, 2019

Tech Infrastructure != Many organizations divide their technology stack between front-end and back-end systems and place an API boundary between the two. I’m including all IT resources “in front of” the API layer in the organization’s technical infrastructure. Value Stream. Half-Agile Transformations.

Technical Review 118

Technical Review Agile Infrastructure Cadence 118

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. Work is then incrementally completed and kept track of through daily stand-up meetings, and the sprint is reviewed afterward to see what can be improved next time.

Agile 125

Agile Technical Review Cadence Software Review 125

MPUG

MARCH 8, 2021

We also previously explored the differences between iterative and incremental development with an example. An example of this type can be the Scrum framework. It’s usually based on a cadence. An example is the Kanban method , which has its original roots in Lean manufacturing. Flow-based Lean-Agile.

Lean 64

Lean Software Review Technical Review Agile 64

Scrum.org

FEBRUARY 22, 2021

Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. How that is supposed to happen is nowhere described in the Scrum Guide.

Software Review 156

Software Review Technical Review Cadence SCRUM 156

Leading Agile

NOVEMBER 24, 2020

The Assumptions of Scrum. So, what does Scrum say about dependencies? And if you look at the way that Scrum is architected, you’ll notice that it assumes a lot, including that each team: Consists of six to eight people. Owns its technology stack. The Reality of Scrum. Focuses on a particular business problem.

Agile 125

Agile Technical Review SCRUM Cadence 125

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. 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

Scrum.org

JANUARY 30, 2023

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. If technology can pass a Wharton MBA exam , maybe, it deserves some attention. Professional Scrum Master Training w/ PSM I Certificate — Live Virtual Class: February 7-10, 2023.

ChatGPT 209

ChatGPT Agile Artificial Inteligence Consulting 209

MPUG

FEBRUARY 1, 2021

A PMO, like the service providers I mentioned in the example at the beginning of this article, also exists to provide value and insight into project performances. For example, the PMO is responsible for providing the template for use story or the template for Product Review/Demonstration. PMO Definition. Multi-Disciplinary.

Agile 94

Agile PMO Technical Review Cadence 94

Gunther Verheyen

DECEMBER 20, 2019

Scrum, in its more general definition, is a simple framework to help us address complex challenges. Product development is the subset of complex problem domains where Scrum took root first; by explicitly acknowledging software and new product development to be complex work, serving to deliver complex products in complex circumstances.

SCRUM 55

SCRUM Cadence Software Review Technical Review 55

Digite

JUNE 13, 2018

She also shows you how to design your first Kanban Board, with examples. Compared to Scrum, Kanban is a young work-management method. But, for teams that chafe under the strictures of the Scrum process, Kanban can be a freeing alternative. In fact, many Scrum teams use this type of visualization to manage their work.

Agile 110

Agile Technical Review Cadence Software Review 110

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. For example, could a month-long Sprint be too short for accomplishing something meaningful? Source : Scrum Guide 2020.

Technical Review 186

Technical Review Underperforming Technical Team SCRUM Software Review 186

Project Management Essentials

AUGUST 3, 2019

In 2013, Mike Cohn coined the term scrum smells to describe the signs that a scrum team is in trouble. Scrum masters, agile coaches, and even team members can improve their teams’ performance by spotting these warning signs early and taking corrective actions. Who is the Scrum Master or Product Owner?

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

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

MPUG

JUNE 28, 2021

The Massachusetts Institute of Technology (MIT), US, notes in its web-archives that Odissi is two to three thousand years old. Now, you might be thinking what exactly a dance has to do with cadence in Agile? Let’s start first with the definition of cadence. Cadence – Definition and Basics. Working with Single Cadence.

Cadence 115

Cadence Agile Technical Review SCRUM 115

Leading Agile

APRIL 20, 2023

But I think I think it’s important we all know what just kind of Scrum, Agile, the whole world knows that if we have to escalate every decision, it just takes forever. We can make our bottom box bigger with some technologies and some expertise, some experience. So Scrum kind of tries to address that a little bit.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

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. For example, could a month-long Sprint be too short for accomplishing something meaningful?

SCRUM 184

SCRUM Technical Review Software Review Consulting 184

Leading Agile

MARCH 31, 2020

– I was working in my office down in technology Parkway. You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. And it’s not always get better the technology get better the processes, it’s get better producing the outcome. And BPR was about the technology.

Agile 71

Agile Technical Review SCRUM Engineering 71

Leading Agile

JANUARY 21, 2021

And what that means to us is not just teaching people how to do agile or how to do kind of methodologies in this space like say for Scrum or what have you but really like how to create the kinds of organizations that really can do agile really well and really effectively at scale. They’re not thinking often about like team level Scrum.

Sustainability 111

Sustainability Agile SCRUM Technical Review 111

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.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Scrum.org

DECEMBER 7, 2020

TL;DR: The Scrum Product Owner in 58 Theses. The Product Owner theses also address the Product Owner’s part in Scrum events from Sprint Planning to Sprint Review to Sprint Retrospective, and the Daily Scrum. The Product Owner is also the most vulnerable Scrum role. Do you want to get this article in your inbox?

Technical Review 230

Technical Review SCRUM Estimate Cadence 230

Scrum.org

JANUARY 14, 2021

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

Cadence 140

Cadence Technical Review Development Team Review Lean 140

Scrum.org

APRIL 11, 2019

Intended audience: Scrum masters, Product owners, Managers and Agile coaches. I was successful with optimising for feature size that could be delivered in a two-sprint cadence. This approach is ideal to get a cadence from the influx of new features to done, closing the empirical process control loop from design to delivery.

Underperforming Technical Team 153

Underperforming Technical Team SCRUM Development Team Review Software Review 153

Planio

JANUARY 11, 2021

Timing and team cadence: Decouple team cadences whenever possible. Timing and team cadence: Decouple team cadences whenever possible. Agile teams rely on a clear sprint cadence to keep projects moving, remove bottlenecks, and ship great software. Here’s an example of what we’re talking about.

Underperforming Technical Team 88

Underperforming Technical Team Cadence CTO Hire Technical Review 88

Scrum.org

MAY 20, 2020

My fellow PST, Glaudia Califano, and I were sitting in a café (at a time prior to the current lockdown due to Covid-19), having agreed to meet up with a Business Analyst who had reached out to us to have a chat about Scrum and Agile. The purpose of completing PBIs is so the goals of the Scrum team are met. .

Planning 182

Planning Cadence Technical Review SCRUM 182

Leading Agile

JUNE 29, 2023

My dad is a rocket scientist, and we went to Georgia Tech, where they had installed a nuclear reactor. Old ways of working won’t solve it, and simply implementing practices like Scrum, DevOps, FinOps, or ProOps are not sufficient to create the organizations we need for the changes we must make. Let me share an example.

Agile 75

Agile Technical Review Executing Influencer 75

Planio

AUGUST 1, 2022

According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. Therefore, a transformation gets seen as simply applying Scrum or other Agile methods to your same working style and culture. More creativity and innovation.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Wrike

FEBRUARY 20, 2023

It incorporates elements of other Agile frameworks — including Lean product development , Scrum, and Kanban — to optimize project execution efficiency, streamline processes and workflows, and reduce waste in big-sized teams. This includes typical Agile roles such as Product Manager, Scrum Master, and Development Team Member.

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Scrum.org

AUGUST 9, 2022

indicated that there is still a challenging situation between their IT (sometimes called Delivery, Tech, etc.) Technology departments struggle with empathizing with Business, customer-faced teams, not understanding how hard their work is. Regardless of working for Business or Technology, be the first to start. Sprint Reviews.

Technical Review 196

Technical Review Cadence 2005 Initiating 196

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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. This is an example, so I just put functional test XYZ01. In the case of these examples, we’ve chosen to use ours. Lewis’ and James Mills JR.’s Melanie: Hello.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Leading Agile

FEBRUARY 11, 2019

Because the recovery phase was not officially recognized (typically due to time reporting rules that prohibited honesty regarding overtime), management missed the opportunity to learn from experience and repeated the death march pattern again and again. Zombie Scrum describes the impact on delivery teams. Stable Team.

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115