Planio

JULY 4, 2022

Agile ceremonies are the fuel that keeps your development team moving forward. But what if you’re not entirely comfortable managing and running Agile ceremonies? Agile ceremonies get abandoned when teams stop seeing the value in them. What are Agile ceremonies? A ‘quick-start’ guide to the 5 Agile ceremonies.

Agile 88

Agile Technical Review Development Team Review Software Review 88

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. Muscial Interlude) The Challenges of Empowring Agile Teams I’m Dennis Stevens, Chief Methodologist at a company called LeadingAgile.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

International Institute for Learning

SEPTEMBER 8, 2022

Has COVID-19 made you see the need to adopt a more agile way of thinking? Estimating and Applying Points with Agile – How to apply, and when is it done? As early as most of us can recall, we estimate the size/magnitude/amount of effort to do something in time. Presenters: Keynote. Dr. Joe Perez. Tony Johnson.

Underperforming Technical Team 88

Underperforming Technical Team 2022 PMI Project Life Cycle 88

Herding Cats

JULY 16, 2017

The GAO Cost Estimating and Assessment Guide has 12 steps. There are not specific to Agile Software Development. Agile teams, for the most part, are a fixed set of resources, so the spending plan is essentially Flat. Either a Cadence Release Plan or a Capabilities Release Plan. Uncertainty creates risk.

Estimate 35

Estimate Agile Cadence Risk Management 35

Leading Answers

MARCH 7, 2019

Yet when projects use new (to us) technology and tackle problems our organizations have not solved before, then risk, uncertainty, and rates of change will be high. It would be easy (and wrong) to classify all construction projects as candidates for traditional approaches, and all IT projects as needing an agile approach.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Herding Cats

MARCH 12, 2016

Neil Killick posted a good question, what's the common ground for talking about estimates. All estimates have two attributes - accuracy and precision. The values of these two attributes are what those needing the estimates are after. That request comes from those asking for the estimate. 100M, 200M, 500M?

Estimate 46

Estimate Cadence Risk Management Risk 46

Velociteach

FEBRUARY 1, 2023

There is a range of options, from predictive to agile. Complex efforts where the cost of change is low may prefer agile. On agile projects, the product owner represents the customer. Acceptable variances, reporting cadence, and status meetings are addressed in the plan. Agile projects are fundamentally different.

Planning 52

Planning Technical Review Governance Government 52

Leading Agile

AUGUST 19, 2020

Agile isn’t ever really about Agile. In our Business Drivers of Agility webinar series hosted by LeadingAgile CEO, Mike Cottmeyer, Mike dives deep into six key business drivers to uncover how Agile can enable organizations to connect these drivers to better business outcomes. It’s about creating business outcomes.

Agile 100

Agile SCRUM Governance Government 100

Planio

AUGUST 9, 2021

Estimate task time and effort. How do Agile teams create a project schedule? Planio: Best for teams of all sizes (Agile and traditional). But to correctly estimate start and end times , you first need to know what needs to be done at a high level, what resources you’ll require, and a basic outline of their order.

Software Review 78

Software Review Technical Review Estimate Agile 78

Leading Agile

MAY 17, 2021

Velocity, while seemingly a simple measure of team output, is quite often one of the most misconstrued metrics by organizations new to Agile ways of working – by both managers and the teams themselves. The sum of those estimations gets locked in as the committed points for the iteration and should be in the ballpark of the team’s velocity.

Estimate 80

Estimate Cadence Sustainability Executing 80

MPUG

FEBRUARY 19, 2024

This is true whether our organization uses a stage-gate approach, an agile approach, or some hybrid of the two. Euterpe encourages us to embrace experimentation and risk-taking in pursuit of innovation. Projects and project managers must be agile and responsive to evolving circumstances in today’s dynamic business environment.

Underperforming Technical Team 52

Underperforming Technical Team Innovation PMI Cadence 52

Scrum.org

FEBRUARY 22, 2021

You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers. In the attempt to fill Scrum’s product discovery void, product delivery organizations regularly turn to other agile frameworks like lean UX, jobs-to-be-done, lean startup, design thinking, design sprint—just to name a few.

Software Review 145

Software Review Technical Review Cadence SCRUM 145

Digite

MARCH 17, 2017

There is a quote introducing PI Planning content on the Scaled Agile Framework website. A Program Increment is a fixed timebox of 8 to 12 weeks (default being 10 weeks as recommended by Scaled Agile Inc.). The 10 weeks’ time-box encapsulates 5 Agile Sprints or Iterations with each spanning 2 weeks.

Planning 60

Planning Engineering Cadence Risk Management 60

Wrike

JUNE 15, 2023

Getting granular with work projects is important as you’re often faced with pressure from several sources: Time limits Budget constraints Client expectations Stakeholder opinion Without a measured or considered approach to how you’ll tackle both major and minor projects, the risk of falling prey to pressure from any of these sources increases.

Energy 36

Energy Budget Cadence Lean 36

Herding Cats

JULY 27, 2017

We were speaking a Homeland Security yesterday on Agile development in the Federal Government and there was a senior director who brought up a paradigm that resonated with me. Agile and Incremental and Iterative Development and Deployment. The same is true of any agile development of enterprise IT product or service.

Cadence 31

Cadence Infrastructure Governance Government 31

Herding Cats

MARCH 23, 2016

A popular mantra in Agile is deliver fast, deliver often. Where we work and where agile is becoming the norm, we have another view. 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. IT Risk Management.

Planning 39

Planning Cadence Logistics Manufacturing 39

Leading Agile

JUNE 29, 2023

What do we have to do to make Agile tangible for our executives? Are Executives Getting in the Way of Agile? One of the challenges we face is the perception that executives don’t care about Agile. There’s a belief that executives are the number one obstacle to successful Agile transformation in organizations.

Agile 75

Agile Technical Review Executing Influencer 75

Scrum.org

DECEMBER 7, 2020

A Product Owner is an innovator at heart and thus a value creator for customers and organizations if given a chance to work in an agile manner. The main accountability of the Product Owner is driving value for customers and the organization while mitigating risk at the same time. Source: Scrum Guide 2020.).

Technical Review 213

Technical Review SCRUM Estimate Cadence 213

Digite

MARCH 2, 2018

It is then up to them – or some business function like sales or support – to have the conversation with your customers that they need to accept new releases at a certain frequency or they may be at a risk of not getting the support they might need on an old version of the product. At the other end as well, there can be two issues.

Underperforming Technical Team 71

Underperforming Technical Team Software Review Cadence Software 71

Digite

MARCH 2, 2018

It is then up to them – or some business function like sales or support – to have the conversation with your customers that they need to accept new releases at a certain frequency or they may be at a risk of not getting the support they might need on an old version of the product. At the other end as well, there can be two issues.

Software Review 66

Software Review Underperforming Technical Team Cadence Software 66

Scrum.org

APRIL 25, 2022

You can sign up here for the ‘Food for Agile Thought’ newsletter and join 35,000-plus subscribers. ?? Technical excellence is a prerequisite of any form of business agility; preserving this state is a continuous process that requires a steady and substantial investment. Too much estimating: The Developers even estimate sub-tasks.

SCRUM 199

SCRUM Planning Underperforming Technical Team 2020 199

Planio

APRIL 24, 2023

In 2021, the Project Management Institute estimated that by 2030 the global economy would need 25 million more project managers to keep up with the demand for change. Assessing and mitigating project risks 7. Planning sprints and running agile ceremonies 8. Identifying and managing any risks or issues as the project progresses.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

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. Scrum is primarily influenced by the Agile Manifesto which describes the “Agile” value system.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Scrum.org

JANUARY 27, 2020

Too much estimating: The Development Team estimates sub-tasks. Read More : Why Engineers Despise Agile ). Irregular Sprint lengths: The Scrum Team has variable Sprint cadences. Otherwise, transparency will suffer and flawed decisions might be made, reducing value creation and increasing risk.).

Planning 220

Planning Underperforming Technical Team SCRUM Cadence 220

Leading Agile

FEBRUARY 11, 2019

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” Stable Team. Dedicated Team. Team Spaces.

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

MPUG

OCTOBER 16, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 2 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to part two of MPUG’s Agile training series. You’re going to see this coming out at a very fast cadence. Hence Agile, right?

Agile 40

Agile Technical Review Software Review Engineering 40

Leading Agile

OCTOBER 3, 2023

And that’s typically how I think about a lot of the talks that I give because everything in the agile communities about doing it and learning from it and sharing with people and getting feedback and figuring out how to do it better and that kind of stuff. What is an Agile Culture So, here’s the end of the talk.

Governance 62

Governance Government SCRUM Agile 62

Workamajig

JANUARY 11, 2021

Accept: A response to a project risk where the project manager accepts the risk and takes no action to evade it, i.e. 'accepting' the risk. This is usually in case of risks that are unlikely to occur or minor enough so as to not affect the project's outcome. Actual dates are different from planned or estimated dates.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Agile Project Management (#APM). Risk Management (#RM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Business, Technical, Systems, Risk, and Project Management.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

FEBRUARY 8, 2019

We talk about the goals of going agile. The first one is the one around risk, around scope rather. So the team design, interacting with a governance model, focused on the flow of value, and managing those five categories of risk, are what our governance model and our team design do. So let me walk through that a little bit.

Governance 75

Governance Government Cadence Underperforming Technical Team 75

Herding Cats

APRIL 5, 2016

There a popular notions in the agile development world that authors like Hayek and Taleb speak to how software development works. You Can’t Understand Agile Without Understanding Hayek. This is the basis of the Agile Product Roadmap and Product Release Plan (either cadence or capability based). IT Risk Management.

Software Developers 28

Software Developers Software Development Software Review Software 28

MPUG

FEBRUARY 11, 2021

” And often this is part of the agile world. Power BI gets refreshed every month so it has a high cadence. Or send me an email when I’ve got a new risk,” those sorts of things. Or when my non mitigated risks go from zero to one. And how much have we done, that can either be tasks.

Software Review 52

Software Review 2020 Risk Management Governance 52

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. Especially when they released the Sixth Edition, giving this agile guide. You’re like, where’s the risk register?

PMI 59

PMI Software Review Estimate Risk Management 59

Leading Agile

AUGUST 20, 2018

But there’s a risk that people will get excited about automation and get ahead of themselves. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Including appropriate tooling in the automated CI process covers most of the remaining risks in this area.

Software Review 78

Software Review Software Technical Review Development Team Review 78