Gunther Verheyen

JANUARY 27, 2021

Ken had founded this new organization a year earlier, in October 2009. In April 2011, Ken came to Brussels for an event I co-organized for the Agile Consortium Belgium. Although it is not something I had planned for, it looks like in 2011-2012 I ended up being in the eye of the Scrum storm that was sweeping the Netherlands.

SCRUM 103

SCRUM 2012 2010 2011 103

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. Establishing the Performance Measurement Baseline (PMB) , AACE Workshop, Denver, Colorado, April 16, 2011.

2003 54

2003 2011 2008 Performance Measurement 54

Rebel’s Guide to PM

JULY 31, 2017

The PMCamp movement was conceived in Austria in 2009 by Stefan Hagen. The idea finally took off in 2011 when the first PMCamp took place in Dornbirn, Austria and successfully continued through Switzerland and Germany in the following years. Klaus Hofeditz.

2003 193

2003 2009 2008 2011 193

Rebel’s Guide to PM

SEPTEMBER 21, 2016

I declared 2009 the year of the Office Goddess and I wrote a series of posts about how to excel at work. By the way, I refer to La Défense as crummy in this article, but by the time I left I had come to appreciate the arch, the architecture and the little cafés hidden between the offices. And also the massive shopping centre.

2007 150

2007 2009 2008 2010 150

Herding Cats

MAY 10, 2019

5, September/October 2011. 5887, 2009. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011. 532, August 2009. “A Risk Management Methodology for Project Risk Dependencies,” Tak Wah Kwan and Hareton K.N.,

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

5, September/October 2011. 5887, 2009. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011. 532, August 2009. “A Risk Management Methodology for Project Risk Dependencies,” Tak Wah Kwan and Hareton K.N.,

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

OCTOBER 15, 2017

Agile Development of Safety-Critical Software , Matti Vuori, Tampre University of Technology, 2011. A Closer Look at 804, A Summary of Considerations for DOD Program Managers, CMU/SEI-2011-SR-015. IMPLEMENTATION OF NEW ACQUISITION PROCESS FOR INFORMATION TECHNOLOGY SYSTEMS. 217–231, 2017.

Process 39

Process Agile 2011 Aerospace 39

Herding Cats

OCTOBER 24, 2018

Agile process Smell and Root Cause Analysis,” Dave Nicolette, International Conference on Agile Processes and Extreme Programing in Software Engineering, 2009. The Analyzing Method of Root Causes for Software Problems,” Tomomi Kataoka, Ken Furuto and Tatsuji Matsumoto, SEI Technical Review, Number 73, October 2011. “A Lehtinen, Mika V.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

OCTOBER 5, 2018

"A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10 1, January 2011. "A Verhoef, Science of Computer Programming, Volume 74, Issues 11–12, November 2009, Pages 934-988. Quantifying IT Forecast Quality,” J. Eveleens and C.

2012 48

2012 2007 2011 2010 48

Herding Cats

DECEMBER 16, 2017

Forecasting and Simulating Software Development Projects: Effective Modeling of Kanban & Scrum Projects using Monte-Carlo Simulation , Troy Magennis, Focused Objectives, 2011. How Many Licks: or how to estimate damn near anything , Aaron Santos, Running Press, 2009.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Scrum.org

MAY 29, 2020

The reason in 2011, Gojko Adzi introduce a different name to group these practices - “ Specification by Example ". It has moved to enable quality focus on both the product and design by enabling faster feedback loops on several different level, than simply writing tests first before code.

Software Review 134

Software Review Technical Review 2004 2003 134

The Lazy Project Manager

MAY 5, 2016

So for Peter ‘The Lazy Project Manager’ Taylor to be selected as previously covered (Amsterdam 2009, Milan 2010, Washington 2010, Dallas 2011) means 1 x 3 x 3 x 3 x 3 which gives us an 81 to 1 probability, I am quite liking those odds, put me down for ten pounds, it is a reasonable gamble.

PMI 150

PMI 2010 2015 2009 150

Herding Cats

MARCH 11, 2017

“Quantifying Uncertainty in Early Lifecycle Cost Estimation (QUELCE),” Robert Ferguson, Dennis Goldenson, James McCurley, Robert Stoddard, David Zubrow, and Debra Anderson, Technical Report, CMU/SEI-2011-TR-026 ESC-TR-2011-026. 2567-2578, Verona, Italy, 2009. NASA Risk Management Handbook,” NASA/SP-2011-3422, Version 1.0,

2003 46

2003 2014 2015 2011 46

Herding Cats

NOVEMBER 12, 2016

Pink, Drive: The surprising truth about what motivates us (2011). . [2] Agile Conference 2009, IEEE. . [4] Dynamic analysis - analyze flow. [1] Ashkenas, “It’s Time to Rethink Continuous Improvement,” HBR blog [link] (2012). . [3] Jakobsen et al, “Scrum and CMMI – Going from Good to Great: Are you ready-ready to be done-done?”

Agile 61

Agile 2009 2008 2011 61

Digite

JANUARY 7, 2018

hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). hours Published January 12, 2009, by Modus Cooperandi Press). Readers new to Kanban will understand why and how it works, while those with experience will appreciate its fresh perspective and the connections it makes with a range of related models.

Lean 79

Lean Software Review 2010 2014 79

Scrum.org

APRIL 7, 2022

Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. Despite its popularity, the actual empirical evidence for the stages or the order is minimal (Bonebright, 2009). The need for fluid teams. Forsyth, D. Group Dynamics, 5th.

Underperforming Technical Team 165

Underperforming Technical Team 2007 2006 2009 165

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. The journey is still underway today.”.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

ProjectManager.com

MARCH 4, 2022

Changes in the scrum community continued when in 2009 Schwaber left the Scrum Alliance to start up Scrum.org , which offers the Professional Scrum Series. Since then, scrum has taken on a global role in project management with the first publication of the Scrum Guide in 2010, which has been updated in 2011 and 2013.

SCRUM 337

SCRUM Software Review Development Team Review Underperforming Technical Team 337

Velociteach

MARCH 20, 2023

And then as the recession came along, the great recession in 2008-2009, I essentially bought the business from the company I was working with and created Atlas Turf. And we set off, took off running in 2011. We didn’t invent the process, but we somewhat perfected it. Where do you grow the grass?

Logistics 52

Logistics Transportation 2022 Governance 52

Herding Cats

JANUARY 20, 2018

A financial maturity survey in June 2011 showed that over 80% of IT departments capitalize their software development. Capitalization and Amortization of Software Costs (Putra), 2009. I have personally worked far more with IT departments that capitalize than with those who expense.

Software 38

Software 2006 Software Developers Software Development 38

Herding Cats

OCTOBER 16, 2018

"Applicable of Model-Based Systems Engineering Methods to Development of Combat System Architectures," John M.Greenn, 6 th Annual Acquisition Research Symposium of the Naval Post Graduate School: Volume 1: Defense Acquisition in Transition, May 13-14, 2009.

Aerospace 41

Aerospace Engineering 2012 2014 41

Herding Cats

APRIL 4, 2019

Probabilistic Risk Analysis: Foundations and Methods , Tim Bedford and Roger Cooke, Cambridge University Press, 2009. 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. 3421, Second Edition, December 2011.

Risk Management 43

Risk Management Risk 2003 2011 43

Online PM Courses

NOVEMBER 11, 2018

In 2011, the then UK Government decided to privatise the work of the OGC, and transferred ownership of OGC methodologies including PRINCE2 and ITIL to Axelos , a joint venture company, between the Cabinet Office and Capita plc. ITIL 2011 Edition. In July 2011, the OGC published the 2011 edition of ITIL to update the 2007 version.

Technical Review 72

Technical Review 2011 2007 Prince2 72

Velociteach

FEBRUARY 6, 2023

Then in 2011 I actually started a Ph.D. I’ve been working with teams and organizations, helping them be more creative, since about 2009. I don’t have a creative bone in my body. And I was like, “What? Yes, you do.” And I would get really emphatic with them. And anyway, you know, as an adult I started digging more into creativity.

Underperforming Technical Team 52

Underperforming Technical Team Innovation Process Leadership 52

Herding Cats

MARCH 11, 2018

ISO 31000:2009, ISO 17666:2016, and ISO 11231:2010 Risk is Uncertainty that Matters. Cost and time overruns for major defense Acquisition programs: An annotated brief,” Center for Strategic and International Studies , Washington, DC, 2011. The Art of Systems Architecting , Third Edition, 2009. Editors, Springer, 2011.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

APRIL 16, 2019

Deliverables Based Planning: Providing Actional Information to the Program Manager - 11th Annual Rocky Mountain Project Management Symposium , 2009. Dallas MPUG , May 6th, 2009. Increasing Your Project's Probability of Success - Microsoft Project Conference , 2009, September 14-17, 2009.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MAY 7, 2019

Nobel Approaches & Practical Applications, AIT 2011. 2, Second Quarter 2009. “A 3, 25 August 2009. 97, 2009. “An “Development of Simple Effort Estimation Model based on Fuzzy Logic using Bayesian Networks,” Abou Bakar Nauman and Romana Aziz, IJCA Special Issue on “Artificial Intelligence Techniques ? 106–118, 2014.

Estimate 40

Estimate Software Review Software 2012 40

Teamweek

OCTOBER 20, 2019

When the Fiscal Times wrote about its article about permalancers in 2011, it used less than flattering terms like “disposable workforce” and “never-ending temps.” In September 2009, the Bureau of Labor reported only 1.72 The answer is: I’m a permalancer. And the way I work may be the future. What Is A Permalancer?

Software Review 40

Software Review 2009 2011 Healthcare 40

Herding Cats

NOVEMBER 7, 2016

“The Impact of Irrelevant and Misleading Information on Software Development Effort Estimates: A Randomized Controlled Field Experiment,” Magne Jørgensen and Stein Grimstad, IEEE Transactions of Software Engineering , Volume 37, Issue 5, September ‒ October 2011. 400-407, 2009. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.

Estimate 64

Estimate 2006 2005 2013 64