Herding Cats

NOVEMBER 7, 2016

“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). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MARCH 17, 2019

Capabilities Based Planning. Capabilities Based Planning (V2). Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Deliverables Based Planning. Nine Best Practices of Project Management , Software Program Managers Network (SPMN). Planning and Scheduling.

2003 54

2003 2011 2008 Performance Measurement 54

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

MPUG

JANUARY 4, 2021

An Agile project is just a Waterfall project almost entirely implemented using Rolling Wave Planning! For at least twenty years and counting, the world around us has become more and more software driven, and, as a result, more digital. Banks have essentially been software developing organizations for a long time.

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

Scrum.org

MAY 26, 2020

Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. I was responsible for managing software development projects. Developers, because of the growing crunch-culture. Although we didn’t choose to work plan-driven, our approach seemed similar to waterfall.

Agile 97

Agile 2004 SCRUM Software Developers 97

nTask

NOVEMBER 23, 2018

Introduced in 2006, with a major redesign in 2010, the platform serves as a single systematic and flexible solution for all the task management needs of a team. Considered a #1 software chosen by agile teams for software development, Jira makes a pretty strong contender for Smartsheet. Affordable plans.

2019 111

2019 2006 2010 Software Review 111

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 ? As more details get developed, the Cone converges to the actual value. Steve McConnell. Quantifying IT Forecast Quality,” J.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 10, 2019

The Effectiveness of Risk Management: An Analysis of Project Risk Planning Across Industries and Countries,” Ofer Zwikael and Mark Ahn, Risk Analysis , Vol. 255, April 2010. 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. 255, April 2010. 24, 2010. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

Our knowledge of this world - the planned and actual behaviors of the project. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Wrike

NOVEMBER 7, 2018

66% said they choose a project management software based on level of support available. [10]. 68% use the project plan documentation. 53% use project management software. 66% of organizations use PM software to communicate with clients. [17]. Between 2010 and 2020, 15.7 Unrealistic schedule/reactive planning.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Project Pulse Journal

MARCH 25, 2024

Incorporating product management concepts into project planning and execution is recommended to achieve organizational goals. Product Life Cycle Management Managing the life cycle of products from planning and development to launch and sustainment is vital for adapting to evolving customer expectations and technological advancements.

Sustainability 52

Sustainability Development Team Review Innovation 2024 52

Digite

MARCH 12, 2018

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. However, the fact is that software development is a complex activity – perhaps more so than any other type of projects?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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.

2007 34

2007 2012 2009 2010 34

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. Together, we have developed a unique quality control system for Wrike, our lovely project management platform, allowing us to deploy product code to production more quickly and without bugs. Hello, everyone! I’m Alexander, and I’m a QAA manager at Wrike.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

Herding Cats

AUGUST 1, 2018

“Reducing Estimation Uncertainty with Continuous Assessment: Tracking the 'Cone of Uncertainty’” Pongtip Aroonvatanaporn, Chatchai Sinthop and Barry Boehm, Center for Systems and Software Engineering University of Southern California , Los Angeles, CA 90089, ASE’10 , September 20–24, 2010, Antwerp, Belgium, 2010.

2012 29

2012 2007 2010 2006 29

MPUG

JUNE 20, 2022

Examples are software development, new product development, pharmaceutical clinical studies, telecommunication, research and development, education, and government projects. Starting with the 2010-release, Microsoft Project could find the 19?day SuperProject used multiple algorithms to find the tightest schedule.

2010 52

2010 Aerospace Underperforming Technical Team Governance 52

ProProfs Project Management

JANUARY 15, 2021

Here’s how the project kanban board looks like: Kanban technique originated from Toyota’s “just-in-time” (JIT) production system and created by Taiichi Ohno who wanted a simple planning system in place to help them manage and control the production process efficiently. However, after 1940 David J. How Kanban Works. Who Uses Kanban?

Software Review 81

Software Review Technical Review 2004 SCRUM 81

nTask

AUGUST 8, 2019

As the name suggests, Waterfall focuses on planning the lifecycle of the project by dividing the project into distinctive, separate and exclusive parts: In a Waterfall model, each phase must be completed before the next phase can begin. . Diagram 2: Basic Representation of a Typical Waterfall Model for Software Development.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. 1] Control or Economic Law Paperback, Eugen von Boehm-Bawerk, 2010. [2] 4] " Risk Management and Agile Software Development ," Glen B Alleman. Herding Cats: Economics of Software Development.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Herding Cats

NOVEMBER 14, 2018

AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found. This decision model for software development projects addressed: performance, cost, time, and risk. I came to AHP through a seminar by Dr. James T. A Cardinal number says how many of something there is.

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

JULY 24, 2017

Traditional project management approaches, several of which are based on a strong belief in the cone of uncertainty, advocate stronger project control and greater planning. While controls and planning are useful, an overly strict focus can result in attempts to solve the wrong goal. This assumes of course the Plan is credible.

2007 42

2007 2012 2006 2008 42

Herding Cats

APRIL 16, 2019

Planning and Scheduling (#PS). Integrated Master Plan and Master Schedule (#IMPIMS). Product Development (#ProdDev). Agile Software Development (#ASD). Without those, progress to plan can only be measured with the passage of time and consumption of money. Management Processes (#MP). Risk Management (#RM).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

SEPTEMBER 19, 2018

Monte Carlo and Agile Development . There are a number of Monte Carlo Simulation tools for agile software development when you don't have an Integrated Master Schedule, with planned durations, and ranges of values. Harrison, AIP Conference Proceedings , January 5, 2010, 1204, pp. My favorite is Agile Monte Carlo.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

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

Herding Cats

APRIL 8, 2017

In many conversations about managing in the presence of uncertainty - which is the ubiquitous condition for all non-trivial software development projects - the notion that principles, processes, and practices of Engineered Systems appear to be the antithesis of Agile development in some quarters. . 39-58, 1997. [3]

Web Development 37

Web Development Software Engineering Engineering 2010 37

Herding Cats

MARCH 4, 2017

This is an immutable principle that impacts planning, execution, performance measures, decision making, risk, budgeting, and overall business and technical management of the project and the business funding the project no matter the domain, context, technology or any methods. All project work operates in the presence of uncertainty.

2010 28

2010 2007 Estimate Aerospace 28

EasyProjects

SEPTEMBER 24, 2019

The Project Management Institute summarized the agile manifesto as follows: Satisfying customers with timely and accurate delivery of software. Recognizing that project discoveries cannot be eliminated with extensive planning. Scrum is used by software development teams. Plan your Sprints .

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Herding Cats

JANUARY 22, 2017

Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. The Cone IS the Planned reduction of uncertainty as the project proceeds. The Cone is NOT the result of the project's past performance.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. The Cone IS the Planned reduction of uncertainty as the project proceeds. The Cone is NOT the result of the project's past performance.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. Performing better technical planning, and making adjustments to resources based on discrepancies between planned and actual progress.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Workzone

APRIL 30, 2020

In 2010 daPulse, created by Wix.com , joined the vast array of project management tools on the market, and in 2017, daPulse went through a transformation to become Monday.com. Designed to come across as colorful and friendly, Monday aims to help you kick your case of the Monday blues through the use of its software.

2020 38

2020 Software Review Technical Review Software 38

Project Management Hacks

AUGUST 4, 2016

Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. Omitting impacted parties during planning was an early mistake I learned from. I led an effort to develop a risk-based software development process.

2013 28

2013 2003 Technical Review 2010 28

Runrun.it

OCTOBER 1, 2019

The concept originated from software development companies, who found the traditional method of project and workflow management was stifling in many situations. The shared planning and constant communication between team members allow for greater team flexibility. The agile organization and the agile squad. Bank of America.

Agile 20

Agile Software Review Leadership Technical Review 20

MPUG

MAY 24, 2020

We do plan to answer those questions for you throughout the session today. I’ve been working on creating blog posts and videos and giving speeches since 2010. Raphael Santos: So software development projects they basically respond, or they are accountable for 102,000 hours out of those 122 hours.

Software Review 40

Software Review Artificial Inteligence Software Developers Software Development 40

MPUG

OCTOBER 9, 2019

If you have any questions during today’s presentation, please send those over at any time using the chat question box on the GoToWebinar control panel and we do plan to answer those for you at the end of the session today. So the diagram here, that’s kind of on the introduction here, we’ll talk about incremental plans.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

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