Herding Cats

MARCH 17, 2019

Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015. How to Develop Credible Cost & Schedule Estimate.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

MAY 10, 2019

requires making estimates) ? This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005.

Risk Management 38

Risk Management Risk Technical Review 2002 38

nTask

SEPTEMBER 27, 2019

As we have previously discussed that the outsourced software development has increased dramatically in recent years. And since 2005, each year the remote workforce has increased by 10% which makes it 140% in 2019, which is huge. Agile Project Management for Distributed Teams. Velocity Chart. Burndown Chart.

Underperforming Technical Team 92

Underperforming Technical Team Agile Technical Review 2005 92

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. requires making estimates) ? Estimation of Long?Term

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. Some feel that the cone does not provide any value for the work they do and does not match the reducing uncertainty in their estimates. This letter states.

2007 34

2007 2012 2009 2010 34

Herding Cats

SEPTEMBER 25, 2018

Of course, all three of these are operating in the presence of uncertainty and therefore require estimates to be made. Estimates of the aleatory and epistemic uncertainties that create risk to the delivered Value need to be handled. Gregory, Operations Research , 23, 2005. [2] All three pieces of information are needed.

2009 34

2009 Artificial Inteligence 2013 2005 34

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. We develop these reference classes using Agile Function Points. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JANUARY 22, 2017

The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates are needed but are subject to large level of uncertainty. The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

APRIL 4, 2019

So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. I'm not expecting anyone to read all these books.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. An estimate of how long it will take. While cards may have deadlines or estimated times to complete, Kanban is viewed as a continuous flow. As tasks progress, the card is moved throughout the workflow.

Software Review 36

Software Review Technical Review 2005 SCRUM 36