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

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 2010 38

Leading Agile

NOVEMBER 17, 2020

And in that we grew the company where originally, we did a mixture, as you know, between transformation and building custom software solutions. Over time, we grew to focus more, mainly on customer soft, custom software solutions, and eventually Accenture purchased us. So— – We reconnected, yeah. – Interesting.

Technical Review 112

Technical Review Software Review Agile Governance 112

MPUG

JANUARY 4, 2021

I’d like to begin by sharing a brilliant quote that puts the latest project management fashion, Agile, into humbling perspective: “ A Waterfall project is just an Agile (Scrum) project with one huge sprint! For at least twenty years and counting, the world around us has become more and more software driven, and, as a result, more digital.

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

Leading Agile

OCTOBER 3, 2023

When I first started thinking through this idea, I was actually really thinking about the idea of practices because back in 2010, a little bit earlier than that, Jim Kundiff, the Scrum Alliance, and those guys were really popularizing the CSM certification, PMI was doing the PMI ACP or a lot of us were part of that.

Governance 62

Governance Government SCRUM Agile 62

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Organizations that use a methodology: 38% meet budget. VS. Organizations that don’t use a methodology: 31% meet budget. 18% — Delivered within budget. 75% of highly agile organizations met their goals/business intent, 65% finished on time, and 67% finished within budget.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

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. Being able to track the time associated with each and every project is one of the most critical aspects of a project management software. Kanban and Scrum boards.

2019 111

2019 2006 2010 Software Review 111

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. Software Risk Management , Barry W. Hassett and Donald G.

Risk Management 43

Risk Management Risk 2003 2011 43

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 2003 Underperforming Technical Team 42

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. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

MPUG

OCTOBER 9, 2019

But you’ve probably seen this in your career where you have people jumping around going, “Oh, hey, here’s the next silver bullet,” or, “We are going to turn into a scrum or an agile shop.” And so this is where agile kind of fits in and isn’t just necessarily only for software development.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Herding Cats

SEPTEMBER 19, 2018

Flight software is always an issue where we work, so those ranges are wider even more. Getting the software qualified is about the same variability as getting it certified, so the same range is used. This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum.

2010 43

2010 Technical Review Estimate Software Review 43