Scrum.org

FEBRUARY 22, 2021

In the attempt to fill Scrum’s product discovery void, product delivery organizations regularly turn to other agile frameworks like lean UX, jobs-to-be-done, lean startup, design thinking, design sprint—just to name a few. They are supposed to code as it is easier to hire an additional UX designer by comparison.

Software Review 141

Software Review Technical Review Cadence SCRUM 141

Resource Guru

SEPTEMBER 27, 2023

But it does mean a balanced strategy that leans on strong retention practices matters. All too often, projects derail due to lack of project scope, or scope creep sneaks up out of nowhere, jeopardizing the client relationship. Be sure to touch base with them regularly , at a cadence that makes sense for both parties.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Transportation 52

Digite

JUNE 13, 2018

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. Creating Your First Kanban Board.

Agile 110

Agile Technical Review Cadence Software Review 110

Scrum.org

JANUARY 10, 2021

TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Professional Developers create working software.

Software Review 227

Software Review Technical Review Planning Manufacturing 227

Leading Agile

MAY 3, 2023

Scrum teams at the bottom, some sort of orchestration mechanism, the product middle tier, some sort of orchestration mechanism up at the portfolio tier, some linkage to investment tier investment strategy, focusing on the flow of value at each level, understanding lean principles. Are we doing reviews? I think SAFE is fine.

Agile 62

Agile Technical Review Governance Government 62

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 then tying that together into a network and then applying Lean principles to designing an organization that can get stuff done. When did we first meet?

Agile 71

Agile Technical Review SCRUM Engineering 71

Leading Agile

JANUARY 21, 2021

So it’s like the ability to form teams, the ability to create clear backlogs the ability to get to a working tested increment of software at the end of every sprint. So again, I’m anchoring not on feature level agility that we often talk about when it comes like agile software development but how do I pivot an organization?

Sustainability 111

Sustainability Agile SCRUM Technical Review 111

Digite

FEBRUARY 13, 2018

Dave is a Principal Consultant at Depth Consulting Ltd, and Program Director of the KCP Program at the Lean Kanban University. 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. Increments.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Leading Agile

APRIL 7, 2023

That having weekly planning cadences; daily standups, reviews, and retrospectives would give people a reason to get in the same room and collaborate. Things really take off with the advent of the CSM certification and PMI finally recognizing Agile as a legitimate way to do software project management. Total chaos.

Agile 133

Agile Governance Government Underperforming Technical Team 133

Leading Agile

AUGUST 19, 2020

So the first lens or the first set of foundational things that we’re going to talk about when it comes to predictability is the idea of the three things, teams, backlogs, working tested software. They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right?

Agile 102

Agile SCRUM Governance Government 102

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. But unfortunately, few companies can pull it off.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Planio

APRIL 24, 2023

Updating project management software to keep their team on track 9. Learn from their mistakes and lean on them for insights. If you’re working on a complex IT project, you can lean on more detailed techniques such as the Critical Path Method or PERT to provide more granularity. Creating actionable project plans 5.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 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

Digite

MARCH 12, 2018

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals!

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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.” Today, some of the same principles seem to present impediments or unnecessary challenges for many teams and organizations. How can the same principle be a good idea in 2002 and a bad idea in 2019?

Agile 116

Agile Underperforming Technical Team Software Review Technical Review 116

Leading Agile

OCTOBER 3, 2023

And so we ended up with a lot of folks doing standups and sprint planning and story cards and sticky notes and burndown charts and reviews and retrospectives. And so I was thinking about Scrum and so I just lifted this off of Mike Cone’s website and it’s attributed, so I hope he doesn’t mind too much mountain good software.

Governance 62

Governance Government SCRUM Agile 62

Leading Agile

AUGUST 22, 2018

The Slippery Slope of “Yes” In many cases, stakeholders of technical teams ask for everything they can imagine they might need. Let’s say you’re using a two-week cadence, as that’s pretty typical and is what most agile coaches recommend as a starting point. The important thing is the mean cycle time.

Underperforming Technical Team 83

Underperforming Technical Team Cadence Technical Review Software Review 83

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

MARCH 17, 2021

Do they own the technology or do they have dependencies with tons of teams around them? But what I would suggest that it’s only a concern to the extent that we’re a profitable company, that we can put out software when we say we’re gonna put out software or put out product, when we say we’re gonna put out product.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Scrum.org

SEPTEMBER 19, 2020

Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog.

Technical Review 185

Technical Review Software Review Development Team Review Cadence 185

Leading Agile

AUGUST 20, 2018

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Handling merges of code changes made by more than one person.

Software Review 78

Software Review Software Technical Review Development Team Review 78

MPUG

JUNE 1, 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. Today’s PMI activity code, I’ll have up on the screen here in a minute. As I was introduced, I was a software and programming instructor for many years.

PMI 59

PMI Software Review Estimate Risk Management 59