Herding Cats

MARCH 17, 2019

Business, Technical, Systems, Risk, and Project Management. Event-Based Scheduling , 10 November 2006. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008.

2003 54

2003 2011 2008 Performance Measurement 54

Planio

JULY 9, 2020

If you’re looking for a new project management tool, this guide will run you through the basics of what Redmine is, why it’s a great choice for most software development teams, and how you can get it set up and optimized for you! Redmine was launched in 2006 and is still being regularly updated. What is Redmine? Need convincing?

2006 88

2006 2007 Closing Agile 88

Resource Guru

JANUARY 27, 2023

You can collaborate as much as you want, but if you don’t get resource scheduling right, your project runs the risk of failure. That way, you’re reducing the risk of running into unnecessary conflict. The launch of Google Docs back in 2006 sure brought collaboration to a new (much-needed) level.

Underperforming Technical Team 97

Underperforming Technical Team 2006 Project Life Cycle Logistics 97

Herding Cats

OCTOBER 5, 2018

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty," Todd Little, IEEE Software , May/June 2006.

2012 48

2012 2007 2010 2011 48

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Herding Cats

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . Carol Brennan, John Wiley & Sons, 2006.

2007 42

2007 2012 2006 2008 42

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. This letter states.

2007 34

2007 2012 2010 2009 34

Herding Cats

AUGUST 1, 2018

One chapter on the Principles of Risk Management and the second chapter on the Practices of Risk Management. Since reducible and irreducible uncertainties create risk, those uncertainties need to be reduced as the project proceeds for the probability of project success to increase. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). Agile Software Development (#ASD). Business, Technical, Systems, Risk, and Project Management. Those lessons are directly transferable to the management of software development teams.

Technical Review 42

Technical Review Performance Measurement 2003 Governance 42

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. For any Agile development tools (Rally, JIRA, Team Foundation Server) have embedded tools for making these charts. What is the Value at Risk for your Project?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

OCTOBER 11, 2016

I work in the Software Intensive System of Systems domains in Aerospace, Defense, Enterprise IT (both commercial and government) applying Agile, Earned Value Management, Productive Statistical Estimating (both parametric and Monte Carlo), Risk Management, and Root Cause Analysis with a variety of capabilities. Department of Energy.

Performance Measurement 28

Performance Measurement Aerospace 2006 Estimate 28

Herding Cats

JANUARY 23, 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. For software development starts with. maybe a read of the resources of Estimating Agile Software Development may help. Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

AUGUST 22, 2018

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. If we take Tim Lister's advice about managing risk while spending other people's money in the presence of uncertainty, where is the adult supervision here? . . Probably not. .

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

Herding Cats

JANUARY 22, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. This is done by active risk management, through probabalistic decision-making.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Wrike

SEPTEMBER 29, 2022

Wrike was launched in 2006 by founder and software developer Andrew Filev. As the business landscape continues to evolve with technology, we can only look forward and prepare to tackle challenges and project risks head-on. What is Wrike?

2006 36

2006 2011 Budget Software 36

Wrike

AUGUST 3, 2023

While Jira has its strengths — particularly for software developers — it may not provide the full range of features, integrations, and automation a modern organization requires. If you’ve ever been part of a software development team, you’ve probably heard of Jira. But the key here is choosing carefully.

Technical Review 36

Technical Review Software Review Development Team Review Software 36

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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. México, 1 al 3 de Febrero de 2006.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2005 2006 2013 64

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

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9,

Estimate 40

Estimate Software Review Software 2012 40

Digite

AUGUST 14, 2017

Be it the “software development process” or the “employee onboarding process” or “the procurement process” – agility is rapidly becoming a cornerstone of our digital world. What are the key risks in the adoption and scaling of Kanban to drive enterprise agility? The method wars.

Agile 94

Agile Lean 2005 Risk Management 94

Herding Cats

OCTOBER 16, 2018

In ISO 15288 this is the role of the Risk Management Processes. A second Critical Success Factor is the ability to predict what will happen in the future given the model of the project's activities and risks and the alternative designed as well as emerging designs and external processes. . This is the desired outcomes model.

Aerospace 41

Aerospace Engineering 2012 2014 41