Herding Cats

OCTOBER 26, 2018

. † These descriptions fall short for the traditional program manager, not because the principles of agile are lacking, but because the practices of program management are not directly addressed using the software development focused methodologies presented by these authors. ‡ 2, 2005. References . [1]

Agile 120

Agile 2005 2001 Software Developers 120

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. reducible and irreducible ?

Risk Management 35

Risk Management Risk Technical Review 2002 35

ProjectManager.com

MARCH 21, 2019

He literally wrote the book about it, It’s All in How You Slice It , which came out in 2005. The idea of a user story as it applies here comes from software development and product management. A user story is an informal description of one or more software features, written from the perspective of an end user in plain English.

Technical Review 287

Technical Review 2005 Software Review Development Team Review 287

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

nTask

AUGUST 18, 2019

Geo-scientific Software Development Projects- Dishansh 2005. Dishansh 2005 is a software that calculates spatial relations by plotting planer and linear structural features, for seismological and geotechnical interpretations. Background. The Process. Network diagram was constructed and the critical path identified.

2005 100

2005 Underperforming Technical Team Technical Review Estimate 100

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 2006 2005 2013 64

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. Flint, School of Management, Working Paper Series, September 2005.”. 61, September 2004.

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

MARCH 17, 2019

Business, Technical, Systems, Risk, and Project Management. 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.

2003 54

2003 2011 2008 Performance Measurement 54

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. Reduces risks. Agile Project Management for Distributed Teams. Greater client satisfaction.

Underperforming Technical Team 92

Underperforming Technical Team Agile Technical Review 2005 92

Herding Cats

SEPTEMBER 25, 2018

Estimates of the aleatory and epistemic uncertainties that create risk to the delivered Value need to be handled. The handling of the risks created by these uncertainties and the residual risk still present after the handling is complete need to be part of the assessment of the alternatives. Keeney and Robin S.

2009 34

2009 Artificial Inteligence 2013 2005 34

Rebel’s Guide to PM

SEPTEMBER 26, 2016

In parallel, organisations demand greater project collaboration capabilities to deal with more challenging projects and improved portfolio analytics to better manage portfolio risk but cannot find an all-in-one tool to satisfy all their needs. She graduated in Mathematics and with an MBA in Global Management.

Software Review 150

Software Review Software Technical Review PMI 150

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. IT Risk Management.

2007 34

2007 2012 2009 2010 34

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 Underperforming Technical Team Governance 42

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

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

ProjectManager.com

MARCH 21, 2019

He literally wrote the book about it, It’s All in How You Slice It , which came out in 2005. The idea of a user story as it applies here comes from software development and product management. For example, if you attach too much detail to the user story then you run the risk of distracting the team. What Is a User Story?

2005 31

2005 Agile Lean Risk Management 31