Herding Cats

MAY 10, 2019

Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. 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. reducible and irreducible

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. Effective Risk Management 2nd Edition, Edmund Conrow, AIAA, 2003.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. in Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. And we all know.

2003 46

2003 2014 2015 2011 46

MPUG

NOVEMBER 20, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for half a PMI PDU in a technical category and the MPUG activity code for claiming that is on the screen now. Kyle: Excellent.

Technical Review 40

Technical Review Software Review 2003 Construction 40

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. This is probably due to the difficulty of measuring many teams over a long period of time. This effect is stronger for smaller teams than larger teams. Bradley et. References.

Underperforming Technical Team 168

Underperforming Technical Team 2007 2006 2009 168

Velociteach

OCTOBER 2, 2023

Since 2003, Jim has been the principal of JP Stewart Consulting, and he’s a certified PMP, and he possesses multiple agile certifications. We had daily stand-ups, and we had sprint reviews and everything. We got along pretty well, but he was the manager of the software. Thank you for voting for us. What is it?” He was so driven.

Underperforming Technical Team 90

Underperforming Technical Team Risk Management Technical Review Agile 90

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

Leading Agile

OCTOBER 3, 2023

And so we ended up with a lot of folks doing standups and sprint planning and story cards and sticky notes and burndown charts and reviews and retrospectives. And so I was thinking about Scrum and so I just lifted this off of Mike Cone’s website and it’s attributed, so I hope he doesn’t mind too much mountain good software.

Governance 62

Governance Government SCRUM Agile 62

Leading Agile

MARCH 17, 2021

So I got involved with agile back in like 2003 and I was working in this company called CheckFree. I talk about things like predictability quality, early return on investment, cost savings, innovation, product fit. Now, how do we get them to go out and be more innovative? Some people think it is and I get it right.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

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

International Institute for Learning

APRIL 20, 2022

Piney, presented at PMI® Global Congress in 2003 (Ref. [3]), 2021) in Harvard Business Review (Ref. [4]). The ideal way to close the virtuous circle would be to find the way to quantify with a prize/benefit due to the positive contribution brought by the distinguished employees. This would be the sign that the success is shared.

Risk 59

Risk 2003 Aerospace 2022 59

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.

Technical Review 43

Technical Review 2010 Estimate Software Review 43