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. Davis, Russell D.

Planning 109

Planning 2007 Technical Review 2009 109

Wrike

JANUARY 12, 2024

Jeff Kinney’s hit children’s book series, Diary of a Wimpy Kid , was first released in 2007 and is still rolling out installments each year. Today, we’re going to discuss the ins and outs of the NPD process, an effective method that can accelerate innovation, bring new ideas and designs to market, and propel you to success.

Innovation 36

Innovation Process Technical Review Artificial Inteligence 36

Scrum.org

APRIL 7, 2022

As we will see below, current scientific models for team formation underscore the need for time and frequent interaction to allow teams to develop the tissue that makes them high-performing. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner.

Underperforming Technical Team 170

Underperforming Technical Team 2007 2006 2009 170

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 204

2002 SCRUM 2007 2003 204

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

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

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

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 ? The program management processes should seek to reduce uncertainty in the variable of the project. 37–48, 2007. Eveleens and C.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

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. I will explain the peer review at the end of this article.

2017 173

2017 2018 2016 SCRUM 173

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. 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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Epicflow Blog

JANUARY 12, 2021

They work closely with portfolio office managers to oversee all processes are in line with the objectives and all tasks are accomplished according to the requirements. . This type of knowledge covers the understanding of the processes, job duties of all employees, rules, market trends that are peculiar for this professional environment. .

PMO 82

PMO 2007 Controlling Construction 82

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

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . 37–48, 2007. . 37–48, 2007. . Laird and M.

2007 42

2007 2012 2006 2008 42

Herding Cats

AUGUST 1, 2018

Specific actions to reduce the Episuncertaintiesnaties and Margin to handle the Aleatory uncertainies are part of any good project management process. . The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Herding Cats

NOVEMBER 5, 2018

In software development, those managing the project have some understanding the market forces (from their marketing departments), the technology (from their engineering department), and how to manage in the presence of Aleatory and Epistemic risk (the managers running a successful firm). Software projects are non-ergodic.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Rebel’s Guide to PM

SEPTEMBER 26, 2016

Moving from traditional to contemporary approaches to project management activities, companies that adopt a linear, phase-by-phase, project management style will probably decline in favour of faster, more iterative and lighter approaches that are driven more by results than processes. Implementation Issues.

Software Review 150

Software Review Software Technical Review PMI 150

Planio

JULY 9, 2020

If you’re looking for a new project management tool, this guide will run you through the basics of what Redmine is, why it’s a great choice for most software development teams, and how you can get it set up and optimized for you! And since 2007, that community has included the Planio team! What is Redmine? Reliability.

2006 88

2006 2007 Closing Agile 88

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

JULY 7, 2018

In project management and especially the software development project management domain, making decisions is always about making decisions in the presence of uncertainty. Uncertainty is always in place for the cost, schedule, and the technical attributes of any software project.

2007 30

2007 Estimate Software Developers Software Development 30

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 222

2015 2014 2004 Influencer 222

Herding Cats

JULY 7, 2018

In project management and especially the software development project management domain, making decisions is always about making decisions in the presence of uncertainty. Uncertainty is always in place for the cost, schedule, and the technical attributes of any software project.

2007 28

2007 Estimate Software Developers Software Development 28

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. Stewart, ACTEX Publications, 2006.

Risk Management 43

Risk Management Risk 2003 2011 43

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

Online PM Courses

OCTOBER 14, 2018

Serving the project management community since 2007 with fresh project management articles every day! Agile Alliance is a nonprofit organization dedicated to promoting the concepts of Agile software development as outlined in the Agile Manifesto. Software development for 40 years. PM Blogs and Bloggers.

PMO 74

PMO Technical Review Underperforming Technical Team PMI 74

Herding Cats

APRIL 16, 2019

Management Processes (#MP). Agile Software Development (#ASD). While many of the presentations have similar titles, the content is focused on a specific set of processes and practices, while the principles are the same, since they are Immutable. . Management Processes. Project Performance Management (#PPM).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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

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

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 4, 2017

The uncertainty is always there, it doesn't go away with specific actions in specific domains, or with the use of any tools, processes, or practices. If they are not reducing, then the project is headed for trouble, the and management processes of the project has failed to performance its job. . 37–48, 2007. The COCOMO 2.0

2010 28

2010 2007 Estimate Aerospace 28

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. So individuals and interactions over processes and tools. And remember, agile is kind of born out of the need for technical project management or in many cases, software development.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

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

MPUG

DECEMBER 4, 2019

So let me go ahead and put in a few resources and let’s just talk through the process. Could probably be done through custom software development and using an Excel workbook that a company’s each project, or something like that. I’m not aware of any personally. Kyle: Thanks Dale. How do I know this?

Software Review 52

Software Review Initiating Software Closing 52