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”). The presidents are always dead presidents.

Software 38

Software 2006 Software Developers Software Development 38

Project Pulse Journal

MARCH 25, 2024

Continuous improvement is common in manufacturing companies like Ford and Toyota, which integrate activities across the value chain by optimizing steps, enhancing technology, and creating more value. Sustainable living plan 2010 to 2020: Summary of 10 years’ progress. 2020, May). link] Vereckey, B. 2021, December).

Sustainability 52

Sustainability Innovation Development Team Review 2024 52

nTask

AUGUST 8, 2019

This helped us to simplify how nTask project management software can be used for solving such issues. Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. Waterfall is a popular SDLC project management model. Background.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

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. 255, April 2010. 24, 2010. “A México, 1 al 3 de Febrero de 2006. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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 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. 24, 2010. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

Teamweek

NOVEMBER 26, 2018

Unless the seller or manufacturer is a household name, growth is generally slow at the beginning. At this stage, there is not likely to be much competition, and if the public embraces the product, the manufacturer has a rare opportunity to create a monopoly. Stage One: Introduction. There is a silver lining behind all this cloudiness.

Software Review 40

Software Review Manufacturing Technical Review Underperforming Technical Team 40

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. And if the competitor is shipping software with greater value, how does the Cone impact that? 37-48, 2007. 37-48, 2007. Thesis, University of Southern California, August 2012.

2007 34

2007 2012 2009 2010 34

Wrike

AUGUST 14, 2020

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. His book on Kanban , published in 2010, is still one of the most comprehensive resources out there for technology-focused projects.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. And remember, agile is kind of born out of the need for technical project management or in many cases, software development. But it is clearly not limited to just software.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40