Digite

MAY 15, 2018

Inspired by Steve Porter’s efforts to bring process practitioners closer together and educate Scrum practitioners, I’m writing a shadow series of posts that will follow the Kanban and Scrum – Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Digite

MARCH 12, 2018

Also, we have quite diverse roles in the team (i.e., In the usual Scrum process, the P.O. We started with a single Kanban board, but with 2 separate swim lanes for the product manager and the dev team – see below – Planning Lane for the Product Owner. Dev Lane for the main dev activity.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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.  Information radiators can show any data the team wants to display.

Agile 135

Agile Planning Underperforming Technical Team Development Team Review 135

MPUG

DECEMBER 28, 2020

An Increment happens when a backlogged item meets the DoD. The new guide clearly informs that Sprint Reviews should not be considered “gates” for releasing value. As there can be multiple Increments, the sum of all these Increments are presented to the (key) stakeholder at the Sprint Review. Introduction of Cadence.

Cadence 116

Cadence SCRUM 2020 Agile 116

Velociteach

MAY 10, 2023

More recently, the profession has grappled with two intertwined questions: Should principles or processes govern project management? Processes describe the inputs, tools, techniques, and outputs used to execute project activities. A toolkit is a collection of techniques and practices used within the project processes.

Lean 88

Lean Cadence PMI 2001 88

Scrum.org

OCTOBER 2, 2018

Heck, many of the companies I meet these days still work that way. The Increment that had to be potentially releasable caused you a lot of pain as you were trying to improve your processes and capabilities, implement Continuous Integration, and finally gain the ability to actually have a releasable Increment each Sprint.

Cadence 134

Cadence Development Team Review Software Review Technical Review 134

MPUG

SEPTEMBER 4, 2023

The attitude to risk The risk attitude of your customer, client, users, or sponsor will dictate not only what risks you are willing to accept (risk tolerance), but also the intensity of your risk management processes. Project Level Risk Management in Agile Projects We can describe the core project risk management process in many ways.

Risk Management 98

Risk Management Risk Agile Technical Review 98

Scrum.org

OCTOBER 2, 2018

Heck, many of the companies I meet these days still work that way. The Sprint Increment that had to be potentially releasable caused you a lot of pain as you were trying to improve your processes and capabilities, implement Continuous Integration, and finally gain the ability to actually have a releasable Increment each Sprint.

Cadence 127

Cadence Development Team Review Software Review Technical Review 127

Leading Agile

JULY 3, 2023

We need to obtain buy-in, address ambiguity, and navigate the process. 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. So get numbers.

Software Review 111

Software Review Fractional CTO Technical Review Agile 111

Planview

JUNE 1, 2021

It can be challenging to expand Agile practices beyond IT and development teams. At the same time, our traditional planning processes cannot keep up or sustain us anymore: The annual plan is most on-strategy the day you finish it. Q: How do you structure big Program Increment planning meetings – virtually?

Cadence 148

Cadence Logistics Lean Agile 148

Leading Agile

JULY 28, 2022

And whether you are producing software or some other product, the process can be applied to many different contexts. Agile Transformation can go beyond software development and improve any organization’s operations to achieve its desired business outcomes. The Process of Producing Working, Tested Product.

Agile 123

Agile Technical Review Cadence Software Review 123

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. (And Sprint review ceremony. Agile is an umbrella term for different iterative and feedback-driven software development processes. And why do they matter?).

Agile 88

Agile Technical Review Development Team Review Software Review 88

Wrike

SEPTEMBER 25, 2023

Cadence and synchronization: Teams should work in fixed iterations, known as sprints, and synchronize their work to deliver a consistent flow of value. This cadence allows for regular feedback and course correction, so that teams stay on track and deliver high-quality results.

SCRUM 36

SCRUM Cadence Development Team Review Software Review 36

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. Incremental delivery of software also mitigates risk and maximizes the opportunity to learn from a business, process, and technical perspective.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Planio

APRIL 24, 2023

Assessing and mitigating project risks 7. Updating project management software to keep their team on track 9. In everyday terms, a project manager’s job is to oversee, coordinate, and lead their team from project kickoff to handoff. Using the chosen project management process to track progress and budget.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Scrum.org

JANUARY 10, 2021

Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Without a regular cadence of delivery of working software any belief that you will get a usable increment is misguided at best. Professional Developers create working software.

Software Review 224

Software Review Technical Review Planning Manufacturing 224

Planio

NOVEMBER 11, 2020

Like showing up to the final exam without studying or standing up at a meeting only to discover you’re not wearing any pants? Now, what if that dream became your team’s reality? If you feel like your team keeps making the same mistakes over and over, they probably are. Who should be at the sprint retrospective meeting?

Underperforming Technical Team 135

Underperforming Technical Team Development Team Review SCRUM Risk Management 135

Wrike

FEBRUARY 20, 2023

The Scaled Agile Framework (SAFe) is an Agile project management framework focused on flexibility, continuous iteration and improvement, and cross-functional collaboration between teams and stakeholders. 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

Agilemania

DECEMBER 2, 2021

Apply cadence and synchronize with cross-domain planning. Alignment of all the teams towards a common goal: Team alignment is the process of ensuring that all the cross-functional teams are dedicated to a common goal. Cross-Team Dependencies: Cross-team dependencies become a source of constant pain.

Technical Review 98

Technical Review Agile Software Review Lean 98

Teamweek

APRIL 29, 2020

These two systems seem fairly similar when you first look at them, but there is a lot more to each of them than meets the eye. This makes managing workloads easier for teams, which is one of the reasons why they are so popular among agile development teams. Kanban is often used when Scrum doesn’t work for a team’s needs.

SCRUM 59

SCRUM Cadence Software Review Development Team Review 59

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. Make Process Policies Explicit. Origins of Kanban.

Agile 110

Agile Technical Review Cadence Software Review 110

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. Start with an Agile pilot project.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Leading Answers

MARCH 7, 2019

Consider the process of designing a new car or home. We have a combination of creative goals (produce something new and appealing) and engineering goals (meet specifications, constraints). The process is likely to be iterative and adaptive. Integrating with the COTS software was a hybrid process.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Planio

AUGUST 9, 2021

How can you optimize your entire team so people aren’t waiting for other tasks to finish? The ‘scheduling’ part of a project schedule should be a collaborative process. Ask each person to help estimate their workload, uncover dependencies, and set deadlines for due dates. Why the project manager?

Software Review 78

Software Review Technical Review Estimate Agile 78

Herding Cats

APRIL 16, 2019

Management Processes (#MP). 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. Management Processes. Planning and Scheduling (#PS).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

AUGUST 19, 2020

In this webinar, we discuss how to create more predictability so we can meet our commitments to customers, and build trust with everyone from internal stakeholders, to customers, to our entire market. And so, predictability is really all about figuring out how to make and meet commitments and how to do what you say you’re going to do.

Agile 89

Agile SCRUM Governance Government 89

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. There’s always a process. Well, it’s important to have a good process.

Agile 40

Agile Technical Review Software Review Engineering 40

Leading Agile

MARCH 17, 2021

And then the process developed a point of view around kind of why companies were jacking it up. And so one of the things that I’ve learned, meeting with the C-suite and candidly selling people on the idea of how to do this. They do daily stand-ups, they do reviews and retrospectives. It was just why agile fails.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62