Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109

Planning 2007 Technical Review 2009 109

Herding Cats

MAY 10, 2019

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. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp.

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.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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. agile retrospectives).

Software Review 121

Software Review 2004 2012 PMI 121

Herding Cats

MARCH 17, 2019

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

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. To become agile, it is important to implement the feedback loops.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

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

This is the motivation for short work intervals found in agile development. . Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects,” Dana Roberson and Mary Anne Herndon, 10 th Annual CMMI Technology Conference And User Group , November 5 – 8, 2012, Denver, CO. The probability of something happening.

2003 46

2003 2014 2015 2011 46

Gunther Verheyen

FEBRUARY 27, 2024

As the earlier excerpt shows, it was this book that introduced the idea of applying the practices described by Takeuchi and Nonaka to software development. The authors explain why the waterfall model doesn’t work for software development, and they offer possible alternatives, among them (what they call) Scrum.

SCRUM 71

SCRUM 2004 Software Review 2019 71

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

Herding Cats

MARCH 11, 2018

IEEE Transactions of Software Engineering, 1 (1984): 4-21. By the way, the pure conjecture that agile enables late changing requirements to not have a significant impact on the cost and schedule of the development project is completely lacking any testable evidence outside of personal anecdotes of agile advocates.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

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.), Standish Group, 2015). Nisbett, R.

2015 219

2015 2014 2004 Influencer 219

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’. Being there. and Heylighen, F.

2002 199

2002 SCRUM 2007 2003 199

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. We are uncovering better ways of developing “products” by doing it and helping others do it. Agile Manifesto, 2001.

2001 213

2001 Software Review Technical Review Underperforming Technical Team 213

Herding Cats

APRIL 4, 2019

Paul Chavas, Elsevier Academic Press, 2004. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Effective Opportunity Management for Project: Exploiting Positive Risk , David Hillson, Taylor & Francis, 2004.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

APRIL 16, 2019

Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). 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

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

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