Scrum.org

DECEMBER 18, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002).

2010 229

2010 SCRUM 2002 2004 229

Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991.

Software Developers 46

Software Developers Software Development Estimate 2006 46

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

Gunther Verheyen

DECEMBER 17, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996) The paper “SCRUM: An extension pattern language for hyperproductive software development” by Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber and Jeff (..)

2010 141

2010 SCRUM 2002 2004 141

Online PM Courses

SEPTEMBER 16, 2018

You want to embrace Agile as part (or maybe all) of your Project Management practice. Which Agile Certification program should you follow? Classifying the Agile Certification Providers. I have also included the Axelos PRINCE2 Agile qualifications here. Tier 1: Principle Promotors of Agile Project Management.

Certification 114

Certification Agile Prince2 PMI 114

Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Analysis of fault generation caused by stress during software development. In Achieving Quality in Software (pp. burnout relationship in software development teams. This post is part of our “in-depth” series.

2004 227

2004 2010 2009 2016 227

The IIL Blog

MAY 17, 2023

This included working with the project team by employing skills such as team development, empowerment, facilitation, and motivation. The Introduction of Agility In the late 90s there were many stories of large-scale project failures, specifically in the IT space. Agile projects value responding to change over following a plan.

Aerospace 147

Aerospace Technical Review Underperforming Technical Team Governance 147

Herding Cats

NOVEMBER 12, 2016

The paper Agile Base Patterns in the Agile Canon , Daniel R Greening, 2016 49th Hawaii International Conference on System Sciences is an important contribution to the discussion of agile at scale in organizations beyond 5 developers at the table with their customer. The Agile Cannon is composed of 5 elements.

Agile 61

Agile 2009 2008 2011 61

Herding Cats

OCTOBER 15, 2017

A popular toss off aphrase in some agile circles is process reduces agility. I've been in the software development business for 30 years, mostly in the Software Intensive System of Systems world, where embedded systems are 100 times more prevalent than business, web and desktop systems. Coe and Jeffrey H.

Process 39

Process Agile 2011 Aerospace 39

Herding Cats

MARCH 17, 2019

Deliverables Based Planning: Providing Actional Information to the Program Manager , 11th Annual Rocky Mountain Project Management Symposium, 2009. Increasing the Probability of Success , Dallas MPUG, May 6th, 2009. Agile Project Management. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008.

2003 54

2003 2011 2008 Performance Measurement 54

Leading Agile

NOVEMBER 17, 2020

Listen to the Agile Unplugged Podcast on the go! Find and subscribe to Agile Unplugged on: Apple Podcasts. Welcome to our latest episode of the Agile Unplugged podcast with host Mike Cottmeyer, LeadingAgile’s CEO. So we first worked together, I guess it was probably back in like late 2009, 2010. Soundcloud.

Technical Review 112

Technical Review Software Review Agile Governance 112

EasyProjects

SEPTEMBER 24, 2019

What is Agile Project Management? . That is precisely what agile project management is – taste testing the stew at various points to ensure that it’s tasting the way it should. Agile Project Management Defined. Agile project management is an iterative or incremental approach to completing projects. How to be Agile.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

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. 5887, 2009. Project Risk Management: Lessons Learned from Software Development Environment,” Y. Risk Management Papers.

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. 5887, 2009. Risk a Feelings,” George F.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Digite

JANUARY 7, 2018

hours Published January 12, 2009, by Modus Cooperandi Press). A comprehensive guide to Scrumban for applying kanban and pull systems in software development. Probably the earliest treatise on Scrumban, the book describes applying lean manufacturing techniques to software development. By Corey Ladas.

Lean 79

Lean Software Review 2010 2014 79

ProjectManager.com

MARCH 4, 2022

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. Scrum is part of agile software development and teams practicing agile. Scrum Values.

SCRUM 333

SCRUM Software Review Development Team Review Underperforming Technical Team 333

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 ? Little [8] makes the claim that agile methods don't follow the Cone - that is the uncertainty doesn't reduce as the project proceeds.

2012 48

2012 2007 2011 2010 48

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

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. A Correction fixed the immediate non-conformance. All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

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. Google will find each of these for you, as a start to the extensive body of litertaure for estimating agile projects in the presence of uncertainty.

2007 34

2007 2012 2009 2010 34

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

Software 38

Software 2006 Software Developers Software Development 38

Herding Cats

MARCH 30, 2019

Agile software development is framed by a manifesto , a set of 12 principles, several methods. These are all focused on developing software, delivering that software to those paying the developers. Why This Missing Concept is Important to Agile Software Development? .

Software Developers 39

Software Developers Software Development Agile Software 39

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Tuckman’s model remains one of the simplest and easiest to explain models for team development to this day.

Underperforming Technical Team 157

Underperforming Technical Team 2007 2006 2009 157

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

Herding Cats

JANUARY 22, 2017

Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Rebel’s Guide to PM

JUNE 29, 2020

Have you ever heard of a T-shaped developer? It’s a common phrase used in software development where the developer has broad experience in their role but is also profoundly skilled in one specific area. This is a guest post from Charlie Davidson. Charlie Davidson. Either way, your team will appreciate you for it.

2009 340

2009 Prince2 SCRUM Construction 340

Herding Cats

FEBRUARY 4, 2017

Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

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

APRIL 4, 2019

Probabilistic Risk Analysis: Foundations and Methods , Tim Bedford and Roger Cooke, Cambridge University Press, 2009. Software Risk Management , Barry W. Strategic Project Risk Appraisal and Management , Elaine Harris, Gower, 2009. Failure of Risk Management: Why It’s Broken and How to Fix It, Douglas Hubbard, 2009.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

FEBRUARY 23, 2016

This list starts with the earliest posts, beginning in 2009. . That says you're either too lazy to do the estimating, I don't you know how to do the estimating, or you really just want to get going and write software, because that's what you do for a living. Software Estimating Taxonomy. Alternatives to Agile Estimation.

Estimate 39

Estimate Risk Management Finance Software Developers 39

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

MPUG

SEPTEMBER 9, 2020

Satya N Dash: You have also agile record concepts coming into time management that you have a lot of additional concepts such as burn up chart, burn down chart, release planning, story map. As early as 2009, 2010, nearly 11 years before I was working as a PMO. One is a software developer.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

MPUG

NOVEMBER 14, 2019

However, all the reports except for the Agile reports, are also part of the 2013, 2016, and 2019 versions of Microsoft Project. And let’s see that live in action, where I click on new, and I click on for instance, a software development plan. And you will be able to use those reports that I’m going to show you today.

2013 40

2013 Finance 2007 Software Review 40

Leading Agile

JUNE 20, 2018

The idea of a self-organizing team has been promoted strongly since the Agile movement started to gain popularity following the publication of the Agile Manifesto in 2001. Clearly, one of the general views of the authors of the Agile Manifesto is that self-organizing teams tend to produce good results.

Agile 102

Agile Defining 2001 2009 102