Remove Cadence Remove Demo Remove Lean Remove Software Review
article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

Many project managers utilize a Lean-Agile approach when there is high change or churn in project requirements, significant lack of clarity in scope, high complexity to their projects, and/or a larger number of risks associated with such. Two Lean-Agile Types. Iteration-based Lean-Agile. Flow-based Lean-Agile. Flow-based.

Lean 64
article thumbnail

Review People Over Process

Henny Portman

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. In the third section we get an overview of some routine meetings like the daily scrum, demos, governance meetings and teleconferences.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Agile Scrum Roles, Ceremonies, Strategy and Projects

The Strategic Project Manager

The concepts of scrum are powerful in business, not only in software development but also in other areas. This post reviews the basics of agile scrum roles, ceremonies, and their impact on developing strategy and managing projects. Sprint – This is a time box defined for regular and consistent work cadence and delivery.

SCRUM 98
article thumbnail

Creating a Risk-Adjusted Backlog

Leading Answers

Prioritizing based on business value is an example of the lean concept of 'Taking an Economic View of Decision Making.' 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. Taking an Economic View of Decision Making.

Risk 145
article thumbnail

New PM, New Choices

Leading Answers

Approaches like lean, kanban and agile work well in these uncertain, high-change environments. Digital projects—which manipulate intangible data and algorithms—have no production phase since the process of turning code into executable software (the process of compiling code) is automated.

article thumbnail

Team using “Waiting for Release” column on their kanban board

Digite

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.

article thumbnail

Kanban = Continuous Delivery? Not Necessarily

Digite

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.