MPUG

MARCH 8, 2021

In this article, we will explore some of the practical problems faced by Lean-Agile practitioners during development of a new product or service and/or the building of a solution. Earlier, in one of my articles, I had mentioned that Agile is both iterative and incremental in nature. It’s usually based on a cadence. Flow-based.

Lean 64

Lean Software Review Technical Review Agile 64

Scrum.org

SEPTEMBER 28, 2020

In this article you will read a detailed review how. Explanation of effort estimation and planning poker. Pokering a small and a large story, gives us two benchmarks for relative estimation of the whole PBL using the magic estimation technique. Startup program details. The Kick-off. Sprint planning.

SCRUM 186

SCRUM Estimate Initiating Cadence 186

nTask

OCTOBER 13, 2021

These are the main questions we will be addressing in this article. When it comes to user statistics, it has been estimated that integrating customer experience can generate $700 million in 3 years for companies that earn $1 billion. In Kanban methodology , there are seven cadences and each of them is implemented via a meeting.

Cadence 78

Cadence 2021 Risk Management Risk 78

Leading Answers

JANUARY 16, 2021

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them. While profit is not their goal, usually an economic impact figure can be estimated for the outcomes they aim to achieve. What is a Risk-Adjusted Backlog? The Economics of Risk Management.

Risk 145

Risk Underperforming Technical Team 2006 2012 145

Wrike

MAY 23, 2023

The Product Owner presents the product backlog, while the team estimates the amount of work that can be completed during the sprint. By having a regular cadence of meetings, the team can stay on track with the project goals and make necessary adjustments along the way. Let Wrike elevate your project performance today.

Agile 36

Agile Software Review Cadence Estimate 36

Velociteach

FEBRUARY 1, 2023

This article presents a framework for modeling project context and considerations for tailoring. Acceptable variances, reporting cadence, and status meetings are addressed in the plan. Team size is known, and the project duration can be time-boxed which simplifies estimating the project’s time and cost and monitoring its performance.

Planning 52

Planning Technical Review Governance Government 52

Leading Answers

MARCH 7, 2019

I wrote this article about the choices of approach we have and ways for new PMs to navigate them.). Likewise, there are defined, repeatable IT projects that can (and have been) successfully managed using meticulous planning, detailed estimation, and formal change control procedures. Consider the process of designing a new car or home.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

MPUG

FEBRUARY 19, 2024

Collaboration between project sponsors and stakeholders to develop the scope and best strategy is required for success, including estimations of time and costs. The project will have a pace, sometimes a swift cadence, and sometimes a variety of paces, sometimes fast and sometimes slower. Project management is a collaborative sport.

Underperforming Technical Team 52

Underperforming Technical Team Innovation PMI Cadence 52

Herding Cats

MARCH 17, 2016

Elliott could provide answers to these questions to our clients, when he suggests that estimates are worthless. . What's your Estimate to Complete and Estimate at Completion for those working demos for all the Capabilities I need to start down the path to breakeven for the software I'm paying you to build? Related articles.

Cadence 42

Cadence Estimate Software Engineering Engineering 42

Herding Cats

JULY 29, 2017

Related articles. Why Guessing is not Estimating and Estimating is not Guessing. Estimating Processes in Support of Economic Analysis. Herding Cats: Capabilities Release or Cadence Release. Estimating and Making Decisions in Presence of Uncertainty. This is called Software Engineering Economics.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

Herding Cats

MARCH 7, 2016

Cadence Release - when a fixed period ends, go with what is ready to go. Cadence Release paradigm, is a flow-based approach. The variability of the development work is minimized through the planned cadence. Focusing on meeting the needs of the customer or market is key to success in the Cadence approach.

Cadence 39

Cadence Agile Underperforming Technical Team Governance 39

Scrum.org

FEBRUARY 22, 2021

Shall I notify you about articles like this one? Apparently, there is a difference in the inspect & adapt cadence when product strategy and Sprint Backlog are compared to each other. The product roadmap needs to be adapted to the learnings from running product experiments regularly in an appropriate cadence to meet that standard.

Software Review 144

Software Review Technical Review Cadence SCRUM 144

Herding Cats

JULY 27, 2017

So when you hear Continuous Integration (CI) and Continuous Delivery (CD) as buzzwords , ask can you show me your Product Roadmap and Release Plan (either Capabilities release plan or Cadence release plan). Related articles. Why Guessing is not Estimating and Estimating is not Guessing. Deadlines Always Matter.

Cadence 31

Cadence Infrastructure Governance Government 31

Scrum.org

JANUARY 30, 2023

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. Shall I notify you about articles like this one? A rough estimation of the budget required. TL; DR: Agile Transformation with ChatGPT or McBoston?

ChatGPT 190

ChatGPT Agile Artificial Inteligence Consulting 190

Leading Agile

APRIL 20, 2023

As the world of business increases in complexity, it will take more than user stories, estimation, and OKRs to build a trustworthy system that management can delegate into. And teams have a cadence where they’re operating with intent but within constraints. ” Like, what the heck does that even mean? What would you go do?

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Scrum.org

NOVEMBER 16, 2023

Understanding the differences in right sizing and same sizing and how they can affect your organization is the topic of today’s article. Right-sizing in Agile refers to the practice of customizing the size of work items in your backlog to match their inherent complexity and effort required to the time interval of your cadence.

Cadence 233

Cadence Estimate Agile Software Developers 233

Leading Agile

AUGUST 13, 2018

We did our short-term planning last week and we came up with an idea of what work we would be able to complete in the next iteration or cadence. People who have been using lightweight methods for years still talk about improving their estimation skills as a remedy for “failing” to force reality to conform with their predictions.

Software Review 98

Software Review Technical Review Cadence SCRUM 98

Herding Cats

MARCH 23, 2016

The Plan for the delivery of value is shown in the Product Roadmap and implemented in the Cadence Release Plan, or sometimes in the Capabilities Release plan. Related articles. Why Guessing is not Estimating and Estimating is not Guessing. Where we work and where agile is becoming the norm, we have another view.

Planning 39

Planning Cadence Logistics Manufacturing 39

Wrike

JUNE 15, 2023

Without resource management tools that let you allocate your budget accordingly, you could easily exceed your initial estimate. Your head is full of ideas for articles, videos, and social media posts, yet you can’t figure out how to put it all together.

Energy 36

Energy Budget Cadence Lean 36

Project Management Essentials

AUGUST 3, 2019

If the product owner is not available to work with the team full-time, then look for second-best options: Assign someone to be responsible for the administrative tasks associated with the product owner role; Establish a regular cadence where the product owner meets with the stakeholders to build and review the product backlog; and.

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Digite

FEBRUARY 13, 2018

Continuing our theme of helping Agile teams understand the Kanban Method, so they can effectively adopt it for their improvement efforts, I am again honored to publish a guest article by another great friend of ours – Dave White. You will enjoy this excellent article. Many Kanban teams have a Queue replenishment cadences.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Scrum.org

APRIL 25, 2022

Shall I notify you about articles like this one? Too much estimating: The Developers even estimate sub-tasks. Remember: the purpose of estimating is to identify misalignment among the Developers regarding the What and How of items from the Product or Sprint Backlog. So don’t waste your time on that.

SCRUM 199

SCRUM Planning Underperforming Technical Team 2020 199

Scrum.org

DECEMBER 7, 2020

Do you want to get this article in your inbox? Roadmap planning is—like Product Backlog refinement—a continuous effort, just at an extended cadence. Product Owner Theses: Product Backlog, Refinement, Work Items, Forecasts, and Estimations. Estimations also allow forecasting a window of availability for work items.

Technical Review 213

Technical Review SCRUM Cadence Estimate 213

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 story point estimating or are we using planning poker? It happened with RUP, it happens with SAFe, it happens with Scrum, it happens with everything. Is there a product owner? Are we doing reviews?

Agile 62

Agile Technical Review Governance Government 62

Scrum.org

JANUARY 27, 2020

Do you want to get this article in your inbox? Too much estimating: The Development Team estimates sub-tasks. Irregular Sprint lengths: The Scrum Team has variable Sprint cadences. Sprint Planning is a core event, defining how your customers’ lives will improve with the next Product Increment.

Planning 220

Planning Underperforming Technical Team SCRUM Cadence 220

Leading Agile

AUGUST 19, 2020

We’re starting to see HBR articles written more than one. We typically want to have those stories estimated, right? Maybe we’re great at doing user stories and estimation and kind of release planning level stuff. And the guys that sign that thing, they changed the world. They understand the acceptance criteria.

Agile 100

Agile SCRUM Governance Government 100

Herding Cats

AUGUST 5, 2017

The answers to each of these questions require making estimates in the presence of uncertainty. No Point Estimate of Cost or Duration can be Correct. The use of point estimates for durations and costs is the first impulse in an organization low on the project management maturity scale. Related articles.

Risk Management 42

Risk Management Risk Estimate Underperforming Technical Team 42

Leading Agile

JUNE 29, 2023

Now, let’s talk about why estimating in hours is absolutely critical for what they’re responsible for and what cannot be done without it. Here are some books you need to read, try this article, attend this conference, or go to this two-day course. It’s crucial to get the executives to stop thinking that way.

Agile 75

Agile Technical Review Executing Influencer 75

Herding Cats

APRIL 5, 2016

This is the basis of the Agile Product Roadmap and Product Release Plan (either cadence or capability based). Related articles. Five Estimating Pathologies and Their Corrective Actions. Five Estimating Pathologies and Their Corrective Actions. Why Guessing is not Estimating and Estimating is not Guessing.

Software Developers 28

Software Developers Software Development Software Review Software 28

MPUG

FEBRUARY 11, 2021

Power BI gets refreshed every month so it has a high cadence. At the top we’ve got China then India, and we’ve got a UN continental region, a UN statistical subregion, a population estimated, obviously at 2018, and one of 2019. And you see there’s different licenses for the Power BI service.

Software Review 52

Software Review 2020 Risk Management Governance 52

MPUG

OCTOBER 16, 2019

You’re going to see this coming out at a very fast cadence. A lot of times I like to have fun, certainly in doing estimating. But there are people who are building tools, but they remember the competency of what’s being organized, structured and delivered is on a very different cadence. Add a bucket.

Agile 40

Agile Technical Review Software Review Engineering 40

Leading Agile

FEBRUARY 11, 2019

High WIP levels and failure to recognize delivery capacity, identify scarce resources, and consider estimates led to intense pressure to deliver late in the project schedule. Ron Jeffries’ classic article, “We Tried Baseball and it Didn’t Work” , is an amusing and yet chillingly accurate description of this situation.

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

MPUG

JUNE 1, 2022

In addition to that, as well as the PMI standards plus to lead the way for the immediate processes, the techniques when it comes to things like estimating or requirements management and things along those lines. What’s deliverable, cadence, project phase? Development approaches that are consistent with project deliverables.

PMI 59

PMI Software Review Estimate Risk Management 59

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. This excellent article by Yaniv Nissenboim describes the value, work flow, and infrastructure for a practical CI/CD pipeline for embedded software products. The company wanted to automate their dispatching process.

Software Review 78

Software Review Software Technical Review Development Team Review 78