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

Scrum.org

SEPTEMBER 19, 2020

There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. 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. Sprint Reviews are a zone free from death by PowerPoint.

Technical Review 188

Technical Review Software Review Development Team Review Cadence 188

Scrum.org

APRIL 11, 2019

I advise to start finding one person to be the single Product Owner for all teams. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements. The Product Owner should develop an inspiring vision and a plan to make it happen.

Underperforming Technical Team 141

Underperforming Technical Team SCRUM Development Team Review Software Review 141

Scrum.org

NOVEMBER 7, 2018

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. SAFe has a cadence at the Team and Program levels.

SCRUM 113

SCRUM Development Team Review Technical Review Cadence 113

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

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

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

MPUG

DECEMBER 28, 2020

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. The diamond shapes in the cadence stream denote the Sprint Reviews.

Cadence 116

Cadence SCRUM 2020 Agile 116

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 119

Software Review Fractional CTO Technical Review Agile 119

Scrum.org

OCTOBER 2, 2018

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. A lot of people see the Scrum Sprint as mainly a release cadence.

Cadence 134

Cadence Development Team Review Software Review Technical Review 134

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

Scrum.org

OCTOBER 2, 2018

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. A lot of people see the Scrum Sprint as mainly a release cadence.

Cadence 127

Cadence Development Team Review Software Review Technical Review 127

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

International Institute for Learning

APRIL 19, 2023

Essential SAFe is the core configuration and is designed for managing a program of 5-12 agile teams. To coordinate the teams, SAFe applies cadence and synchronization. Cadence means all teams are aligned to a standard, two-week delivery cycle. DA defines “process blades” to describe common enterprise capabilities.

Agile 59

Agile Cadence Certification Lean 59

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. He not only owns the process for PI planning but also the logistics, tooling, and agenda.

Cadence 148

Cadence Logistics Lean Agile 148

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

Leading Answers

JANUARY 16, 2021

Assessing the chances of loss or gain occur throughout all forms of business and relies on taking an economic view of decision making. I do not think the teams have been weak at threat avoidance. Instead, I believe many projects leave a lot of development team sourced opportunities unactioned.

Risk 145

Risk Underperforming Technical Team 2006 2012 145

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 125

Agile Technical Review Cadence Software Review 125

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

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

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 227

Software Review Technical Review Planning Manufacturing 227

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. Think of your favorite mobile apps (e.g., What are the principles of SAFe?

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Teamweek

APRIL 29, 2020

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. These roles are for the development team, Scrum master and product owner. Scheduling.

SCRUM 59

SCRUM Cadence Software Review Development Team Review 59

Planio

NOVEMBER 11, 2020

Sprint retrospectives are a powerful opportunity to highlight opportunities for change, generate meaningful improvements to your workflows and processes and speed up future projects, and stop your team from falling into the same traps. Improvements to processes like your daily scrum. How long should a sprint retrospective last?

Underperforming Technical Team 135

Underperforming Technical Team Development Team Review SCRUM Risk Management 135

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. Long term planning and iterations for big teams. Decentralize decision making.

Technical Review 98

Technical Review Agile Software Review Lean 98

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

Leading Answers

MARCH 7, 2019

Consider the process of designing a new car or home. The process is likely to be iterative and adaptive. Then, once the design is agreed upon, the process of production is typically more defined and repeatable. The development team wants interesting work using new technology and skills to further their craft.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

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

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

Agilemania

NOVEMBER 30, 2021

Planning and Execution of Program Increment: A SAFe Agilist has envisioned a roadmap for the success of the Agile Development and successful SAFe implementation process. They start strategic planning as a lead which sets the plan for the Development team to realize the goal of becoming an Agile organization.

Cadence 98

Cadence Lean 2011 Construction 98

Leading Agile

AUGUST 19, 2020

And they’re counting on the fact that all of the planning processes, all the project management, or all the Agile or all whatever, is going to help them make promises, okay? They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right? But you get the idea, right?

Agile 87

Agile SCRUM Governance Government 87

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. They do daily stand-ups, they do reviews and retrospectives. Within that context, we have to create safety for the development teams to tell the truth. It was just why agile fails.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Agilemania

MAY 17, 2021

The framework lets the executives get involved in the entire process, which means the system has the support of executives. Agile coaches help train development teams, product owners, executives on the agile methodology and oversee the development of agile teams to ensure effective outcomes for the organization.

Agile 98

Agile Lean SCRUM Development Team Review 98

Agilemania

MAY 17, 2021

The framework lets the executives get involved in the entire process, which means the system has the support of executives. Agile coaches help train development teams, product owners, executives on the agile methodology and oversee the development of agile teams to ensure effective outcomes for the organization.

Agile 84

Agile Lean SCRUM Development Team Review 84

Leading Agile

AUGUST 20, 2018

Reviewing code by eyeballing it to ensure compliance with coding standards. The company wanted to automate their dispatching process. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Even better: It was the right process. They followed the advice.

Software Review 60

Software Review Software Technical Review Development Team Review 60