Gunther Verheyen

DECEMBER 17, 2020

Scrum has been around for a while, they say. The Scrum Guide holds the definition of Scrum, they say. The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? What else happened along the road to the way that Scrum is defined and represented?

2010 141

2010 SCRUM 2002 2004 141

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. About the author: Charlie Davidson is a Senior Digital Project Manager and Scrum Master, based in Oxfordshire.

2009 343

2009 Prince2 SCRUM Construction 343

Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. You can observe implicit coordination in Scrum teams when you look at how work moves across a Scrum board, or on- and of the Sprint Backlog. This is also why the Scrum framework includes the Definition of Done.

2004 225

2004 2010 2009 2016 225

International Institute for Learning

JULY 7, 2022

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). Fitzgerald, B (2009). Creativity in agile systems development: a literature review.

Innovation 59

Innovation Agile 2002 2001 59

Scrum.org

MARCH 16, 2020

I believe Agile software development is more than ready to use new forecasting techniques to express uncertainy to narrow their decision-making process. These new forecasting techniques are not based on estimations but historical data, thus saving time on the part of developers to focus on what they do best.

Agile 192

Agile Underperforming Technical Team 2030 Estimate 192

Scrum.org

APRIL 7, 2022

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. Despite its popularity, the actual empirical evidence for the stages or the order is minimal (Bonebright, 2009). Forsyth, D.

Underperforming Technical Team 155

Underperforming Technical Team 2007 2006 2009 155

The IIL Blog

MAY 17, 2023

Systems development projects, especially those with a large software component, would spend years gathering requirements, designing, and building a system that would be plagued by changes and completely outdated by the time it was launched. 2 weeks until IIL’s Agile & Scrum 2023 Online Conference!

Aerospace 147

Aerospace Technical Review Underperforming Technical Team Governance 147

Digite

JANUARY 7, 2018

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. hours Published January 12, 2009, by Modus Cooperandi Press). Kanban and Scrum – Making the Most of Both – Henrik Kniberg & Mattias Skarin.

Lean 79

Lean Software Review 2010 2014 79

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . 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). Better Sure than Safe?

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. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

5887, 2009. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y. 532, August 2009. Risk a Feelings,” George F. Loewenstein, Elke U.

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. 532, August 2009. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

OCTOBER 15, 2017

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. the Secretary of Defense shall develop and implement a new acquisition process for information technology systems.

Process 39

Process Agile 2011 Aerospace 39

Herding Cats

NOVEMBER 12, 2016

Establish a Zero backlog approach to planning - Scrum creates Sprint Backlog. Highly effective Scrum teams have seven items in Sprint Backlog. Jakobsen et al, “Scrum and CMMI – Going from Good to Great: Are you ready-ready to be done-done?” Agile Conference 2009, IEEE. . [4] Limit WIP to improve value flow.

Agile 61

Agile 2009 2008 2011 61

Online PM Courses

SEPTEMBER 16, 2018

Scrum Alliance. Scrum Alliance was the first (2001) major organization to promote scrum, and to offer its certifications. Its Certified Scrum Master (CSM) qualification is still the most widely known agile certification. Scrum Alliance claims to have issued over 750,000 certifications.

Certification 113

Certification Agile Prince2 PMI 113

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. Kirkeboen, G., &

2003 46

2003 2014 2015 2011 46

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

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Deliverables Based Planning: Providing Actional Information to the Program Manager - 11th Annual Rocky Mountain Project Management Symposium , 2009. Dallas MPUG , May 6th, 2009.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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

EasyProjects

SEPTEMBER 24, 2019

For example, Microsoft, which began with one team in 2008, several teams in 2009, some 25 teams in 2010 in the Visual Studio group, then several hundred teams in the Developer Division in 2011, and then a commitment to take Agile across the whole organization around 2014. Scrum is used by software development teams.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Leading Agile

JUNE 20, 2018

The Scrum Alliance, an organization that supports an Agile-aligned method known as Scrum, offers an explanation of self-organizing teams , written by Nitin Mittal. But ultimately we’ll see how the idea ties back to self-organizing teams in the context of Agile software development. Let’s keep looking.

Agile 81

Agile Defining 2001 2009 81

Herding Cats

FEBRUARY 23, 2016

This list starts with the earliest posts, beginning in 2009. . New Books for Work - making multiple decisions, forecasting and simulating software development projects, forecasting methods and applications. How to Estimate Software Development - Update. Estimating Software-Intensive Systems.

Estimate 39

Estimate Risk Management Finance Software Developers 39

MPUG

SEPTEMBER 9, 2020

Satya N Dash: In addition to that, I have seen management practitioners when they create a plan, they make a lot of mistakes, without any software tool, in this case Microsoft Project. 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

Leading Agile

NOVEMBER 17, 2020

So we first worked together, I guess it was probably back in like late 2009, 2010. Talk to me about some of the challenges that you had taking it straight from a software development perspective. I wasn’t actually trying to help anybody get better at software development per se, or product management per se.

Technical Review 86

Technical Review Software Review Agile Governance 86