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. The primary document produced from the Capabilities Based Planning process is the Concept of Operations.

Planning 109

Planning 2007 Technical Review 2009 109

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Software development is (generally speaking) very complex. It is a mental process and a limited mental resource (Ashcraft, 2002).

2002 190

2002 SCRUM 2007 2003 190

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

Herding Cats

MARCH 11, 2018

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. Now To Risk Management. Epistemic uncertainty ? from the Greek ??????µ?

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Agilemania

FEBRUARY 23, 2023

Concerns were voiced in the IT operations and software development sectors from 2007 to 2008 about the old software development paradigm that split operations from developers regarding how code was distributed and supported. DevOps was formed by combining the concepts of development and operations.

Software Review 52

Software Review Technical Review Certification 2007 52

Scrum.org

FEBRUARY 25, 2020

When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. The moment was perfect in my career.

2017 172

2017 2018 2016 SCRUM 172

Leading Agile

JUNE 27, 2018

The impression was reinforced strongly when I attempted to bridge the divide by participating in the academic tracks of agile and technical conferences in the 2007-2008 time frame. They weren’t professional software developers, and they were pretty new at the whole process of doing research, as well.

Software Review 123

Software Review Technical Review Underperforming Technical Team 2007 123

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. The Future of Systems-and Software Development.

Estimate 64

Estimate 2006 2005 2013 64

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

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

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. IEEE Transactions on Software Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999.

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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Planio

JULY 9, 2020

Comfort knowing you’re always running the latest, most stable version of the software. Agile Project Management out of the box. It was developed to help teams collaborate on the tasks, bugs, features, and steps needed to complete a project, visually track their progress, and plan their next steps using Gantt charts. Reliability.

2006 88

2006 2007 Closing Agile 88

MPUG

OCTOBER 9, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 1 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. It’s not all or nothing.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Rebel’s Guide to PM

SEPTEMBER 26, 2016

Project management practitioners are looking for new lean and agile project management tools to support their day-to-day work and often seek them outside the tools that their organisations offer them. In other words, the market is confusing: Stick with what you know but host it in the cloud, or move to a new digital offering?

Software Review 150

Software Review Software Technical Review PMI 150

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Herding Cats

AUGUST 1, 2018

We're writing two chapters in an upcoming Project Management Book, with a working title, The Gower Handbook of Project Performance for Agile, Waterfall and Everything in Between , edited by Mark Phillips. The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10.

2012 29

2012 2007 2010 2006 29

Herding Cats

APRIL 4, 2019

Software Risk Management , Barry W. Strategic Risk Taking: A Framework for Risk Management , FT Press, August 12, 2007. Applied Software Risk Management: A Guide for Software Project Managers , C. Ravindranath Pandian, Auerbach Publications, 2007. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM.

Risk Management 43

Risk Management Risk 2003 2011 43

Online PM Courses

OCTOBER 14, 2018

And we mustn’t forget that there are other widely used hashtags in the #PMOT community, like #Agile, #PMO, and #PMP. Donnie’s Article at Online PM Courses: A Simple Way to Develop Interpersonal Skills for Project Managers. We make Agile teams become amazing, check out our free online masterclass: agilesumo.com.

PMO 72

PMO Technical Review Underperforming Technical Team PMI 72

Scrum.org

AUGUST 17, 2020

People often fail to understand this fallacy because they underestimate how much of their behavior and their outcomes are influenced by randomness (Taleb, 2007). Survival bias happens when failures are ignored when you are evaluating if a process or decision is the right one (Schermer, 2014). How to reduce this bias. Survival bias.

2015 212

2015 2014 2004 Influencer 212

Digite

MARCH 12, 2018

In the usual Scrum process, the P.O. I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. Also, we have quite diverse roles in the team (i.e.,

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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. Gano, Atlas Books, 2007. A Correction fixed the immediate non-conformance.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 16, 2019

Management Processes (#MP). 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). Management Processes. Planning and Scheduling (#PS).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Planio

JULY 22, 2020

Project management is as much about people as it is about processes. To make a complex practice like project management simpler, the most recent version of the PMBOK breaks the core project management processes down into five sections: Initiating : Defining a new project or a new phase of an existing project. Author: Brett Harned.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

MPUG

OCTOBER 24, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 3 webinar being provided by MPUG for the convenience of our members. I think this is kind of exciting to be learning a little bit more about not only just the Agile disciplines, but the technologies that go together. I think this will be helpful.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40

Herding Cats

JANUARY 22, 2017

The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. With this paradigm we have logically connected project management processes with Control System processesIf the variances, created by uncertainty going outside the UCL and LCL.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. With this paradigm we have logically connected project management processes with Control System processesIf the variances, created by uncertainty going outside the UCL and LCL.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

The Measures that are modeled in the Cone of Uncertainty are the Quantitative basis of a control process that establishes the goal for the performance measures. Again this is simple statistical process control, using feedback to take corrective actions to control future outcomes - feedforward. Resources. [1] Air Force. [4]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

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