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. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109

Planning 2007 Technical Review 2009 109

NimbleWork

APRIL 11, 2024

A Brief History The Work Breakdown Structure (WBS) has its origins in the mid-20th century, evolving primarily in industries such as defense, aerospace, engineering, and construction. Today, the WBS remains a fundamental tool in project management, with applications across various industries and methodologies, including software development.

Software Review 52

Software Review Development Team Review Risk Management Defining 52

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. 61, September 2004.

Estimate 40

Estimate Software Review Software 2012 40

Epicflow Blog

JUNE 12, 2023

A phase-gate process (also known as a stage-gate process) is an approach to managing projects and developing products, which breaks the whole procedure down into phases separated by gates. Currently, the approach is used to manage R&D, product or software development projects or other large and complex initiatives.

Process 52

Process Underperforming Technical Team Software Review Technical Review 52

Planio

NOVEMBER 15, 2018

Get peer reviews and make revisions. Development support: This could be functional and technical specifications, software development guides, or simply procedures and tools to help your developers do their jobs. Deadline and final deliverables: When is it due and what format will it be in?

Technical Review 159

Technical Review Underperforming Technical Team Software Review Aerospace 159

Epicflow Blog

MARCH 22, 2024

For example, the aerospace and defense industry is associated with the following risks: Volatility in the geopolitical and economic environment, Competition in the domestic and international markets, Exposure to cyber risks, and others. Speaking of the industry-related ones, risks can be unique or common across industries.

Risk Management 52

Risk Management Controlling Risk Aerospace 52

International Institute for Learning

SEPTEMBER 20, 2022

The risk with larger teams is that they can be more vulnerable to poor communication, fragmentation, and free riding due to a lack of accountability [3]. Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016. This alone is a good reason to pay attention to the two-pizza rule [5].

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

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. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Aerospace/. Project Management Software & Tools. Most-Wanted Features in Project Management Software: 1. Project Failure.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

NOVEMBER 7, 2016

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 ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

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. A Critical Review Of Risk Management Support Tools,” Irem Dikmen, M. 3, March 2002. “The

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

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. This also meant developing software systems to support this effort. And money in the bank is what software development is about.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JANUARY 23, 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. This also meant developing software systems to support this effort. Rarely are software engineers working on science experiments. But what it really says is.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37