Scrum.org

JANUARY 22, 2020

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. Even if a parameter is known, the level of detail may be too deep to be able to manage and control it.

Cadence 200

Cadence SCRUM Software Review Technical Review 200

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. Conducting a meeting: make the path visible and start down it and control the dialogue. The book is divided into four sections.

Software Review 93

Software Review Process Lean Leadership 93

Leading Agile

JULY 18, 2023

Third, how are we reproducing working tests in software? Additionally, we need to consider how we organize teams in the presence of dependencies, how we orchestrate and govern those dependencies, and what we measure and control around the team. These products should have well-architected, well-tested, defect-free code.

Agile 110

Agile Software Review Certification Technical Review 110

Leading Agile

MARCH 31, 2021

It is tempting to throw in the towel and say that encapsulating the value stream is impossible without refactoring the code to eliminate those dependencies, but the reality is that encapsulation of the value stream is still feasible in this scenario.

Underperforming Technical Team 118

Underperforming Technical Team Software Review Technical Review Governance 118

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. Dividing your transformation initiative along the seams of the technical infrastructure will often be a suboptimal approach. Half-Agile Transformations. Is it easy?

Technical Review 117

Technical Review Agile Infrastructure Cadence 117

Leading Answers

MARCH 7, 2019

Likewise, there are defined, repeatable IT projects that can (and have been) successfully managed using meticulous planning, detailed estimation, and formal change control procedures. Having said software development is design phase focused, it’s important to understand most IT projects do more than just software development.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

MPUG

SEPTEMBER 4, 2023

As we will see, agile methods are, to a degree, a response to the kind of risks that software development projects face. What agile adds to this, therefore, is a distinct cadence of its own iterations or drawdowns of tasks into the Work in Progress part of the Kanban Board. This is the uncertainty of the end product.

Risk Management 98

Risk Management Risk Agile Technical Review 98

Rebel’s Guide to PM

AUGUST 6, 2022

It’s fine to have a different cadence at different points in the project lifecycle. If you are expecting the project oversight committee to make a decision at the meeting, make sure that they have information in advance of your meeting so that they can review the different options. Action review and next steps. Key decisions.

Governance 356

Governance Government Risk Management Technical Review 356

Planview

JUNE 1, 2021

A continuous planning cadence – quarterly, monthly, or even weekly – enables organizations to be ready to move fast when change occurs, or new opportunities appear on the horizon. Read on to review some answers to questions asked during the webinar along with a few of our other recommendations.

Cadence 148

Cadence Logistics Lean Agile 148

Agilemania

DECEMBER 13, 2021

The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. Code Quality. Apply cadence and synchronize with cross-domain planning. Empirical process control. In the Scaled Agile Framework, every team member works diligently.

Agile 98

Agile Lean Software Review Technical Review 98

Scrum.org

FEBRUARY 22, 2021

To prevail in today’s game of an accelerated innovation-based competition—software is eating the world—, every organization needs to acquire a holistic understanding of an agile product creation process: A vision leads to a strategy that (probably) results in a portfolio of products (and services). Read More : “ Creating Personas.”.

Software Review 140

Software Review Technical Review Cadence SCRUM 140

Planio

AUGUST 9, 2021

What is the best project scheduling software to use? For example, maybe you need to finish cleaning out old code or squash some lingering bugs before building out new features. Ask each person to help estimate their workload, uncover dependencies, and set deadlines for due dates. Quality control. Who’s going to do it?

Software Review 78

Software Review Technical Review Estimate Agile 78

Scrum.org

MARCH 18, 2019

Dan graciously granted fellow Professional Scrum Trainers permission to use the software for educational purposes. In the remainder of this post I will focus on the key features of the software and highlight how Scrum (and Kanban) practitioners can benefit from using it in their daily (or maybe weekly) routine. Because it is.

Agile 119

Agile Cadence SCRUM Software Review 119

Velociteach

FEBRUARY 1, 2023

The degree is a balance between control and efficiency. All the tailoring dimensions and stakeholder needs inform the level of governance, oversight, and management reviews. Acceptable variances, reporting cadence, and status meetings are addressed in the plan. How frequently are the risks and response strategies reviewed?

Planning 52

Planning Technical Review Governance Government 52

Leading Answers

JANUARY 16, 2021

That could take two weeks and cost $100,000 when factoring in the new software license, the team's burn rate, and the cost of delay to the organization. Fortunately, the cadence of iterations and events such as retrospectives and sprint planning provides all the occasions we need to keep the process going.

Risk 145

Risk Underperforming Technical Team 2006 2012 145

Scrum.org

MARCH 18, 2019

Dan graciously granted fellow Professional Scrum Trainers permission to use the software for educational purposes. In the remainder of this post I will focus on the key features of the software and highlight how Scrum (and Kanban) practitioners can benefit from using it in their daily (or maybe weekly) routine. Because it is.

Agile 93

Agile Cadence SCRUM Software Review 93

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. They are merely visual control systems.

Agile 110

Agile Technical Review Cadence Software Review 110

Gunther Verheyen

DECEMBER 20, 2019

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. Even if a parameter is known, the level of detail may be too deep to be able to manage and control it.

SCRUM 55

SCRUM Cadence Software Review Technical Review 55

Scrum.org

JANUARY 10, 2021

In my last post about Professional software teams creating working software David Corbin made a good point. TL;DR; Your Developers are ultimately responsible for creating done increments of working software. Working Software is not specific to a PBI; it’s applied regardless of PBI to the entire delivery.

Software Review 228

Software Review Cadence Underperforming Technical Team 2020 228

Leading Agile

APRIL 20, 2023

Why is it hard for managers to empower teams they want control? Why do they want control? We say they control the velocity with the backlog, right? And teams have a cadence where they’re operating with intent but within constraints. Some organizations do operations reviews or bigger retrospectives.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Digite

MARCH 2, 2018

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. What is the business context? Support, SLAs, Meeting Market Requirements.

Underperforming Technical Team 71

Underperforming Technical Team Software Review Cadence Software 71

Scrum.org

MAY 16, 2024

Due to their limited scope of ownership (tasks or features) and span of control (single team), all they can maximize is the utilization of their team’s capacity. Whatever Billy decides will be limited to her span of control: her team. They study and do the work in a shared cadence (Sprint). So why not give it a try?

Agile 163

Agile Software Review Cadence Engineering 163

Digite

MARCH 2, 2018

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deployed to our SaaS servers – that cadence is well established. What is the business context? Support, SLAs, Meeting Market Requirements.

Software Review 66

Software Review Underperforming Technical Team Cadence Software 66

Scrum.org

MARCH 11, 2024

Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs within Sprints. It just feels good to solve yet another puzzle from the board, here: coding a new task. Hence, you may notice tickets queueing in the code-review column, for example.

Technical Review 155

Technical Review Underperforming Technical Team Software Review SCRUM 155

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 226

Software Review Technical Review Planning Manufacturing 226

Velociteach

NOVEMBER 14, 2023

Maintaining a Command-and-Control Culture We have been transitioning from an industrial to a knowledge economy for over 60 years. Despite this shift, many organizations are stuck in the top-down, command-and-control culture associated with Frederick Winslow Taylor and Henry Ford. Giving up control and trusting the team is hard.

Underperforming Technical Team 84

Underperforming Technical Team Agile Software Review Cadence 84

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. What are we asking our organizations to measure in control? So you do review and retrospective to say, do a burn down chart. This is what the team does.

Sustainability 88

Sustainability Agile SCRUM Technical Review 88

Planio

JANUARY 11, 2021

Timing and team cadence: Decouple team cadences whenever possible. A major part of project management is adding restraints and order to the chaos of building software. Timing and team cadence: Decouple team cadences whenever possible. Finally, you could avoid company-wide cadence entirely like the team at Gumroad.

Underperforming Technical Team 88

Underperforming Technical Team Cadence CTO Hire Technical Review 88

Scrum.org

MARCH 28, 2022

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. It just feels good to solve yet another puzzle from the board, here: coding a new task. Hence you may notice tickets queueing in the code-review-column, for example.

SCRUM 153

SCRUM Technical Review Software Review Consulting 153

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. A behavior problem.

Agile 133

Agile Governance Government Underperforming Technical Team 133

Planio

MARCH 13, 2023

Standard controls format - just the essentials 2. Rate and summarize each key project control 9. This leaves you at risk of becoming one of the 54% of projects fail that fail due to poor KPI tracking. Lastly, project status reports help you prove good control around your project. Why do they matter?

Underperforming Technical Team 78

Underperforming Technical Team Software Review Technical Review Risk Management 78

Leading Agile

MAY 3, 2023

The roles, the ceremonies, the artifacts, the cadences, all those different things that we model as implementation details. Are we doing reviews? What kind of reviews and retrospectives are we doing and how are we doing them?” It happened with RUP, it happens with SAFe, it happens with Scrum, it happens with everything.

Agile 62

Agile Technical Review Governance Government 62

Digite

MARCH 12, 2018

split across different cities and even countries, though all speak the same language), and getting the know-how under control etc. 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

Scrum.org

APRIL 11, 2019

Delivering working software is perceived as an IT responsibility instead of a Business-IT collaboration. I was successful with optimising for feature size that could be delivered in a two-sprint cadence. Connect the dots by making reporting on market research data and customer feedback data a mandatory item of the Sprint Review.

Underperforming Technical Team 141

Underperforming Technical Team SCRUM Development Team Review Software Review 141

Leading Agile

MARCH 31, 2020

You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. And that was about the time that I was starting to develop the teams backlogs, working testing software. How do I do six reviews and retrospectives? How do you like fix it? – Yeah. – Yeah. – Yes.

Agile 63

Agile Technical Review SCRUM Engineering 63

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. We do reviews and retrospectives, right? They’re not dependency free.

Technical Review 90

Technical Review Agile SCRUM Governance 90

Planio

OCTOBER 15, 2020

As Zapier ’s data team manager, Muness Castle , explains, people new to remote work can have problems adapting to the lack of a regular cadence, structure, and the connection with fellow teammates: "I've worked ~15 years on co-located teams and the last ~5 on remote teams. Focus on results (and use data to help you).

Underperforming Technical Team 88

Underperforming Technical Team Cadence Software Review Controlling 88