Herding Cats

MARCH 11, 2018

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Now To Risk Management.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

OCTOBER 30, 2018

This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world. This missing document is a root cause of many failures in tradition and agile software development. Davis, RAND National Defense Institute.

Planning 109

Planning 2007 Technical Review 2009 109

Scrum.org

MAY 26, 2020

Barry : Failed software development projects. I was responsible for managing software development projects. Developers, because of the growing crunch-culture. I have a pretty diverse background, from scientific training to software development and from running a company to being part of a team.

Agile 100

Agile 2004 SCRUM 2010 100

Scrum.org

AUGUST 17, 2020

It happens, for example, when we don’t trust a certain person or group of people, and then only see behavior that fits with our belief (or even interpret it as such) without considering observations where they don’t (Oswald & Grosjean, 2004). 2004), “Confirmation Bias” , in Pohl, Rüdiger F. (ed.), 79 (386): 259–267. Nisbett, R.

2015 223

2015 2014 2004 Influencer 223

The IIL Blog

APRIL 27, 2018

Online gaming collaboration can be traced back to the introduction of the personal computer and software developers and came to life in the early 1990s when the Internet was introduced. Resources: Number of participants, software, and systems required, facilities, etc.

2004 121

2004 Software Review 2012 PMI 121

Scrum.org

JANUARY 27, 2021

In the complex world of Sales, Marketing, and Software Development, we also needed new ways of thinking that would power the same ideas from Toyota and Lean into the high variance world of complex cognitive work. Instead of coming up with best practices, we realise that there are only good practices for the situation at hand.

2001 216

2001 Software Review Technical Review Underperforming Technical Team 216

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’. 2004) _How can we think the complex?Retrieved Their article inspired me to apply the same insights to Scrum and to extend it with my own. Being there.

2002 205

2002 SCRUM 2007 2003 205

Herding Cats

MARCH 17, 2019

An Introduction to IMP/IMS , 17 Oct 2004. 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

ProProfs Project Management

JANUARY 15, 2021

Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. So much that it is being used for other projects besides software development. However, after 1940 David J. Let’s check that out in the next section. Who Uses Kanban?

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Herding Cats

JUNE 24, 2016

This graph is from old 2004 numbers. How to Estimate Software Development. I got the Kindle version, so I have a $10 investment at risk. Let's start with some graphs that have been around and their misinformation that forms the basis of the book. The Chaos Report graph. That's 12 year old numbers. Myth's Abound.

Software Review 44

Software Review 2004 Estimate Budget 44

EasyProjects

SEPTEMBER 19, 2018

My team and I were running a software development company back in 2004 when we realized that our projects needed to be managed in a better way. Once we started using Easy Projects to manage our software development projects, our clients started requesting access to use it for their own work.

Artificial Inteligence 40

Artificial Inteligence 2004 2015 Infrastructure 40

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

2003 46

2003 2014 2015 2011 46

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 2003 Government 42

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. Shrinking The Cone Of Uncertainty With Continuous Assessment For Software Team Dynamics In Design And Development,” Pongtip Aroonvatanaporn,” Ph.D.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

EasyProjects

AUGUST 13, 2018

Ever since Easy Projects’ inception back in 2004, its core product architecture has stayed relatively the same: Web Server (MS IIS) and Database Server (MS SQL). As the product’s complexity, along with our team size, have increased, we had to start looking for better ways to manage our development and deployment processes.

2004 40

2004 2019 Innovation Software Development 40

Herding Cats

APRIL 4, 2019

Paul Chavas, Elsevier Academic Press, 2004. Effective Opportunity Management for Project: Exploiting Positive Risk , David Hillson, Taylor & Francis, 2004. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996. Risk Management in Software Development Projects , John McManus, Routledge, 2003.

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. 61, September 2004. How I Estimate Software Development Projects,” Alvin J.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010. Talat Birgonul, and A. 85 1 Feb 2019. “An

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. 920, November 2004. 255, April 2010. Kwak and J.

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