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

Leading Agile

JULY 3, 2023

As more and more companies scramble to untangle the code of their monolithic legacy software and get it into the cloud, strategic priorities are shifting. 10 years ago, it seemed that a little Scrum here and some coaching there would suffice. I used to run a company that developed unit testing software.

Software Review 119

Software Review Fractional CTO Technical Review Agile 119

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 136

SCRUM Development Team Review Technical Review Cadence 136

Scrum.org

JANUARY 22, 2020

Scrum, in its more general definition, is a simple framework to help us address complex challenges. Scrum is increasingly being discovered as a simple framework to address complex problems and situations other than software and product development. No sustainable agility is achieved.

Cadence 202

Cadence SCRUM Software Review Technical Review 202

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

MPUG

MARCH 8, 2021

An example of this type can be the Scrum framework. It’s usually based on a cadence. As shown in the above figure, there is no regular timeboxed iteration, but incremental delivery can happen in cadence. When you fire a gun in the dark, it’s difficult to aim due to the lack of light. Flow-based Lean-Agile.

Lean 64

Lean Software Review Technical Review Agile 64

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

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. When are Sprint Goals crafted?

Infrastructure 172

Infrastructure Monitoring SCRUM Cadence 172

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

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

Scrum.org

MARCH 14, 2023

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. We have reviewed those ideas in an article on Team Topologies and highlighted some serious drawbacks of such an org design.

Agile 198

Agile Cadence Technical Review Development Team Review 198

Scrum.org

OCTOBER 2, 2018

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. 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. Scrum Theory helps us out here.

Cadence 134

Cadence Development Team Review Software Review Technical Review 134

Scrum.org

OCTOBER 2, 2018

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. 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. Scrum Theory helps us out here.

Cadence 127

Cadence Development Team Review Software Review Technical Review 127

Scrum.org

JULY 31, 2023

They did not have the skills or authorization to make software and configuration changes in the banking systems. The queue of work was huge due to the long waiting times for the work in progress. Tasks belonging to these initiatives got stuck in the worklists of teams in the IT department due to unclear decision processes.

Technical Review 148

Technical Review Software Review 2022 2021 148

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

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

Agilemania

DECEMBER 2, 2021

SAFe endorses alignment, transparency, collaboration, and product delivery involving large size teams.The core of SAFe is based on four bodies of knowledge which are agile software development, lean product development, systems thinking, and DevOps. Apply cadence and synchronize with cross-domain planning. Take an economic view.

Technical Review 98

Technical Review Agile Software Review Lean 98

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

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

Leading Agile

APRIL 24, 2019

This is a slightly broader definition of “front-end” that we normally hear from, say, web app developers. 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. Half-Agile Transformations.

Technical Review 117

Technical Review Agile Infrastructure Cadence 117

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

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 83

Software Review Technical Review Cadence SCRUM 83

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. Do we solve it by putting in specific practices in place like scrum of scrums or dependency boards or like that’s a set of practices.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

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. That was kind of the hypothesis.

Agile 87

Agile SCRUM Governance Government 87

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

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 93

Sustainability Agile SCRUM Technical Review 93

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

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

Leading Agile

APRIL 4, 2023

The Scaled Agile Framework wasn’t exactly what the authors of the Agile Manifesto imagined 20 years ago when they set out to define a better way of building software. It requires the ability to continuously deploy software, to continuously get feedback on it. And by the definition of Agile, it absolutely isn’t, right?

Technical Review 91

Technical Review Agile SCRUM Governance 91

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

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

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

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 99

Agile Underperforming Technical Team Software Review Technical Review 99

Leading Agile

MARCH 17, 2021

And so I’m looking at like all these people that were trying to adopt Scrum and what they were missing was this idea that if we can’t form complete cross-functional teams, giving them really super clear backlogs and give them the ability to produce a working passive increment of software at the end of every sprint, then it would fail.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62