Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Why our brain is not built for software engineering. Although our brain is a marvel of evolution, it has not evolved to excel at the kind of knowledge work (Davenport, 2005) that we actually do most of the time. waterfalls) are very likely to fail.

2002 190

2002 SCRUM 2007 2003 190

nTask

AUGUST 18, 2019

Steps in the PERT Planning Process. This is a straight forward process for most project managers and allows them to efficiently employ project resources. 3. Navy’s Special Projects Office was working on the Polaris missile development program. Geo-scientific Software Development Projects- Dishansh 2005.

2005 100

2005 Underperforming Technical Team Technical Review Estimate 100

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

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

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

Digite

AUGUST 14, 2017

Be it the “software development process” or the “employee onboarding process” or “the procurement process” – agility is rapidly becoming a cornerstone of our digital world. Kanban helps identify process bottlenecks, manage workloads, and predict output based on flow capacity. The method wars.

Agile 94

Agile Lean 2005 Risk Management 94

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

Herding Cats

MARCH 17, 2019

Managment Processes. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008.

2003 54

2003 2011 2008 Performance Measurement 54

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

Scrum.org

AUGUST 9, 2022

between these departments regarding their way of working and processes. Business does not understand the complexity of software development or engineering work. Is it a process? 1 Patrick Lencioni, Overcoming the Five Dysfunction of a Team, 2005. Frequently, they both suffer from. It may happen that. vice versa.

Technical Review 164

Technical Review Cadence 2005 Initiating 164

Wrike

AUGUST 14, 2020

Toyota was looking for a way to improve their engineering and production processes. The Kanban process was the result of this adaptation. . Toyota used physical cards to signal separate steps in their manufacturing process. Anderson is often credited as being the first to implement Kanban in software development in 2005.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

APRIL 4, 2019

Cooper, Stephen Grey, Geoffrey Raymond, and Phil Walker, John Wiley & Sons, 2005. Project Risk Management: Process, Techniques, and Insights , 2nd Edition, Chris Chapman and Stephen Ward, John Wiley & Sons, 2003. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996.

Risk Management 43

Risk Management Risk 2003 2011 43

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

ProjectManager.com

MARCH 21, 2019

He literally wrote the book about it, It’s All in How You Slice It , which came out in 2005. The idea of a user story as it applies here comes from software development and product management. Story mapping, like the larger agile framework, is an iterative process. What Is a User Story? So, it’s time to prioritize.

2005 31

2005 Agile Lean Risk Management 31

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

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. With what appears to be NO understanding of how to estimate, this author ignores the processes used in developing products or services in the presence of uncertainty.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Teamweek

JANUARY 23, 2020

In their words: Founded in 2005 as an intimate gathering of friends DLD (Digital – Life – Design) has developed into Europe’s leading innovation conference for visionaries from around the globe. In their words: The Biggest multitrack Tech Conference of the Netherlands for all software developers. DLD Conference.

Technical Review 52

Technical Review 2020 Artificial Inteligence Software Review 52

MPUG

DECEMBER 4, 2019

We were founded in 2005, and as such, we’re one of the oldest, and most established PPM consulting firms in the United States. So let me go ahead and put in a few resources and let’s just talk through the process. And just to answer your questions, yes, I have been up in the Gateway Arch a couple times. Kyle: Thanks Dale.

Software Review 52

Software Review Initiating Software Closing 52

Leading Agile

NOVEMBER 26, 2018

I’ve seen unit tests that cover an entire executable, a collection of collaborating objects, an end-to-end transaction, an entire batch jobstream, a series of steps in an ETL process, and all kinds of other things that are of large scope and that have lots of tightly-coupled dependencies. Michael “GeePaw” Hill.

Software Review 89

Software Review Technical Review 2005 Executing 89