MPUG

DECEMBER 28, 2020

A new version of Scrum guide was released last month. It’s less prescriptive and seems to be intended for a wider audience group, particularly non-software users. It’s less prescriptive and seems to be intended for a wider audience group, particularly non-software users. It contains commitments for each of the Scrum artifacts.

Cadence 116

Cadence SCRUM 2020 Agile 116

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 163

SCRUM Technical Review Software Review Consulting 163

Velociteach

NOVEMBER 14, 2023

People are encouraged to develop solutions to serve customers and define how the team operates. Even well-meaning scrum masters and managers of agile organizations ask me, “My agile team is struggling. Since only a third of the features in enterprise software are commonly used, delivering incrementally reduces waste.

Underperforming Technical Team 84

Underperforming Technical Team Agile Software Review Cadence 84

Scrum.org

NOVEMBER 7, 2018

SAFe includes Scrum - so how come many Scrum practitioners and thought leaders consider it unsafe? It takes advantage of established frameworks and techniques that work well - Scrum being the first and foremost of those. SAFe's Scrum Master is more of an Agile Team Lead. I hear a lot of questions and claims.

SCRUM 138

SCRUM Development Team Review Technical Review Cadence 138

Scrum.org

OCTOBER 16, 2023

Many teams grapple with the intricacies of Scrum, and one of the most pivotal components is the Sprint Goal. Thanks to our reviewers: Ralph Jocham | Scrum.org TLDR; The Sprint Goal is the heart of Scrum, representing the team's commitment to the value derived from the Sprint's outcome.

Infrastructure 178

Infrastructure Monitoring SCRUM Cadence 178

Scrum.org

JANUARY 22, 2020

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.

Cadence 207

Cadence SCRUM Software Review Technical Review 207

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

Henny Portman

JULY 26, 2020

Furthermore, neither agile or scrum contemplates how the agile team should be connected to a larger organization and to external partners who will likely have differing development processes and cadences. It puts the focus on the software and the related business processes in a powerful way by using different scenarios.

Software Review 93

Software Review Process Lean Leadership 93

Scrum.org

MARCH 14, 2023

Without defining value, no agile transformation is possible. In Scrum terms, this is about improving upon the Definition of Done. 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.

Agile 205

Agile Cadence Technical Review Development Team Review 205

Scrum.org

NOVEMBER 7, 2018

SAFe includes Scrum - so how come many Scrum practitioners and thought leaders consider it unsafe? It takes advantage of established frameworks and techniques that work well - Scrum being the first and foremost of those. SAFe's Scrum Master is more of an Agile Team Lead. I hear a lot of questions and claims.

SCRUM 113

SCRUM Development Team Review Technical Review Cadence 113

Agilemania

MARCH 19, 2021

Scrum vs. Kanban is one of the most trending comparisons in the world of agile methodology! However, while Scrum and Kanban both have differences, their principles are the same. Both Kanban and Scrum will help you to build high-quality products and provide better services with less hassle. Scrum vs. Kanban: The Definitions.

SCRUM 98

SCRUM Lean Software Review Cadence 98

Leading Agile

JULY 28, 2022

They depend on the software or product they produce and their audience or market. Improved Quality of Software or Product. And whether you are producing software or some other product, the process can be applied to many different contexts. They are the ones that must define clear acceptance criteria and definition of done.

Agile 125

Agile Technical Review Cadence Software Review 125

Leading Agile

JULY 18, 2023

If not, then we start measuring things like people trained, teams doing Scrum, or the organization’s sentiment toward Agile to tell us if we’re succeeding. Third, how are we reproducing working tests in software? We also need to define the acceptance criteria of Agile. What is the acceptance criteria for Scrum?

Agile 118

Agile Software Review Certification Technical Review 118

Scrum.org

MAY 14, 2020

In an effort to curb productivity leakage, some managers are turning to software to monitor their people. People and Interactions over tools and software. Agile has been around for a while now, but many firms still see agility as a software development solution. We are Scrum practitioners. Agile isn’t just for software.

Agile 177

Agile Technical Review Software Review Cadence 177

Digite

FEBRUARY 7, 2018

The questioner asked – “I have recently joined a company and to one of the projects that I’m engaged we have this Scrum team that has a mixed backlog (USs and Bugs). Software teams frequently manage products – and that means they are expected to build new features for the product as well as fix defects reported in the product.

Underperforming Technical Team 117

Underperforming Technical Team SCRUM Software Review Cadence 117

Agilemania

NOVEMBER 2, 2021

They consist of 5-11 members who define, build, test, and produce an increment in a short period. Apply cadence and synchronize with cross-domain planning. SAFe isn’t just about delivery or writing code but more about the people and process. SAFe isn’t just about delivery or writing code but more about the people and process.

Certification 98

Certification Agile Software Review Lean 98

MPUG

SEPTEMBER 4, 2023

We learn as we go and take small steps with defined budgets, resourcing, and time-boxes. As we will see, agile methods are, to a degree, a response to the kind of risks that software development projects face. As a result, some people might expect that agile projects have – or even need – no risk management. That is completely wrong.

Risk Management 98

Risk Management Risk Agile Technical Review 98

International Institute for Learning

APRIL 19, 2023

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. To coordinate the teams, SAFe applies cadence and synchronization. They emerged about a decade after the Agile Manifesto.

Agile 59

Agile Cadence Certification Lean 59

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. What usually started in software development can now be extended to the entire company and thus, change the way people collaborate. But it’s not that easy.

Technical Review 100

Technical Review Lean 2011 Cadence 100

MPUG

JANUARY 31, 2022

In the phases with an Agile or adaptive approach, you want to have a combination of adaptive approaches – say a combination of Scrum and Kanban. This is because you used the frameworks of Waterfall, Scrum, and Kanban within a single project! I’ve derived the word ScrumBan by combining Scrum with Kanban. Build the Scrum Part.

Agile 111

Agile Software Review SCRUM Cadence 111

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 144

Software Review Technical Review Cadence SCRUM 144

The Strategic Project Manager

NOVEMBER 7, 2022

To provide an initial taste of agile methods, consider the following list: Scrum – Scrum codifies the ‘pillars and values’ of transparency, inspection, and adaptation. This is most visibly implemented in sprints, with well-established scrum team roles. Scrum – Think about product development.

Agile 52

Agile Software Review Cadence SCRUM 52

Agilemania

FEBRUARY 22, 2021

Scrum vs. Kanban is one of the most trending comparisons in the world of agile methodology! However, while Scrum and Kanban both have differences, their principles are the same. Both Kanban and Scrum will help you to build high-quality products and provide better services with less hassle. Scrum vs. Kanban: The Definitions.

SCRUM 52

SCRUM Lean Software Review Cadence 52

Leading Agile

APRIL 24, 2019

Business agility is what organizations are looking for; agile software development may be one enabling factor in achieving it, but it isn’t the point of a transformation. Such frameworks define a system of delivery, but no system of transformation. Half-Agile Transformations. Comprehensive transformation.

Technical Review 118

Technical Review Agile Infrastructure Cadence 118

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

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

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

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

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

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

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. But unfortunately, few companies can pull it off.

Agile 78

Agile Technical Review Leadership Infrastructure 78

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. What is the Scaled Agile Framework?

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Velociteach

NOVEMBER 20, 2023

You have scrum meetings, you know, you kind of come together for about 15 minutes. A Cadence to Managing Projects BILL YATES: Okay. There’s a cadence. There’s a cadence. Daily scrum meetings on every two weeks after you have your reviews; right? So you think about agile work. What are you working on?

Underperforming Technical Team 99

Underperforming Technical Team Cadence Certification Consulting 99

Digite

MARCH 2, 2018

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. If your unpredictable release schedule is a (perceived) problem, it can be easily fixed by defining an explicit policy to do releases every 1, 2 or 4 or 6 weeks, whatever is acceptable in the business context.

Underperforming Technical Team 71

Underperforming Technical Team Software Review Cadence Software 71

Digite

MARCH 2, 2018

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. If your unpredictable release schedule is a (perceived) problem, it can be easily fixed by defining an explicit policy to do releases every 1, 2 or 4 or 6 weeks, whatever is acceptable in the business context.

Software Review 66

Software Review Underperforming Technical Team Cadence Software 66

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.

Agile 62

Agile Technical Review Governance Government 62