Herding Cats

OCTOBER 15, 2017

A popular toss off aphrase in some agile circles is process reduces agility. In this domain today, Agile processes are the basis of engineering those systems. Scrum, Kanban, even eXtreme Programming are used, guided by higher level directives like the National Defense Authorization Act Section 804 which says.

Process 39

Process Agile 2011 Aerospace 39

Herding Cats

DECEMBER 16, 2017

Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. While some have publication dates that may seem old, the principles in these books are immutable, even for agile projects. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

MARCH 11, 2017

The risk is created when we have not accounted for this natural variances in our management plan for the project. Dealing with Aleatory (irreducible) uncertainty and the resulting risk requires we have margin. An aleatory risk is expressed as a relation to a value. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Scrum.org

AUGUST 13, 2019

How common misunderstandings about the Scrum Roles prevent Scrum Teams to become effective. For an effective Scrum team that statement makes perfect sense. On the flip-side, Scrum defines 3 distinct roles with very specific responsibilities and accountabilities.

2008 21

2008 Certification SCRUM Leadership 21

Scrum.org

SEPTEMBER 11, 2020

Everybody wants to Scale Scrum. So you have a couple of Scrum Teams that are working in adjacent areas and you're starting to face some challenges in delivering value in a coordinated integrative way. This is more or less the time you started searching for "scaling agile" "scaling scrum" and exploring your options.

SCRUM 215

SCRUM 2008 2013 Software Review 215

Planio

MAY 22, 2023

With 80% of companies using Agile project management methodologies to run their businesses, release planning has become more important than ever. What should be included in an Agile release plan? Track your progress with an Agile burndown chart 9. Release too often, and you risk overwhelming your users.

Planning 78

Planning Agile Software Review Estimate 78

MPUG

DECEMBER 23, 2020

So my latest book is the PMO lifecycle, building, running and shutting down, Project Communication tools is my latest communication book, the Tactical guide for building a PMO in way back, and that’s why it looks a little different, but way back in 2008, I published Project Management communication Bible. Do they have a risk log?

PMO 52

PMO Construction Development Team Review Executing 52

Scrum.org

SEPTEMBER 23, 2019

TL; DR: Scrum Master Engagement Patterns. Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. The first article of this series will address the Scrum Master engagement with the Development Team.

Development Team Review 138

Development Team Review SCRUM Software Review Technical Review 138

Scrum.org

NOVEMBER 2, 2018

Have you ever tried to kickstart a “Scrum of Scrums” in an organization? It’s an agile activity which looks like it ought to be a no-brainer for teams…something they’d want to buy into, and of clear value to all. Everyone else seems to have more important matters to attend to than another piece of agile “fluff”.

Governance 139

Governance Government Lean Sustainability 139

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43

MPUG

NOVEMBER 11, 2020

Long back, I think sometime in 2007 or 2008, while I was getting introduced to project management, my first job into a role of a project manager, long back around 213 years before. Satya Dash: The final key point is telling you, a rapid consumption of total float values can indicate a possible slippage of schedule and hence, a schedule risk.

Software Review 52

Software Review Lean SCRUM PMI 52

The IIL Blog

JUNE 28, 2018

According to management guru Peter Drucker, there are only two sources for growth: marketing and innovation [Drucker, 2008]. Innovation requires: An acceptance of significant risk, more so than in traditional project management. The future will be flexible project management models such as those used in Agile and Scrum projects.

Innovation 106

Innovation 2008 2011 2010 106

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. This corresponds with research on autonomous teams, as well as principles of Agile software development.

Underperforming Technical Team 179

Underperforming Technical Team 2007 2006 2009 179

Planio

JULY 22, 2020

Scrum: The Art of Doing Twice the Work in Half the Time. Risk Up Front: Managing Projects in a Complex World. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Epicflow Blog

OCTOBER 20, 2020

According to PMI’s Job Growth and Talent Gap in Project Management 2017-2027 , organizations’ need for project talent has significantly increased since their previous investigation in 2008. Every project manager should have a strong understanding of project theories and methodologies, and be able to apply them in his or her work: Agile, .

Technical Review 98

Technical Review Certification PMI 2027 98

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

Herding Cats

OCTOBER 20, 2017

But just a reminder - All Software Development project work, no matter the method, Kanban, Scrum, Traditional requires making estimates about the future outcome in the presence of uncertainty about that future or the present conditions. IT Risk Management. Herding Cats: Process Reduces Agility? There is no way out of this.

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. 11, November 2008.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . Review on Traditional and Agile Cost Estimation Success Factor in Software Development Project,” Zulkefli Mansor, Saadiah Yahya, Noor Habibah Hj Arshad, International Journal on New Computer Architectures and Their Applications (IJNCAA) 1(3): 942–952.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

SEPTEMBER 19, 2018

Monte Carlo simulation on projects examines all paths through the network of activities or all possible states of the project for the duration, cost, and risk that create impacts on duration and cost. This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum.

Technical Review 43

Technical Review 2010 Estimate Software Review 43