Rebel’s Guide to PM

JULY 11, 2022

If you are a software engineer, show me your software projects. Bad example: Involved in work to deliver a new sales pipeline process and workflow software that supports it. In 6 months we delivered the software and process changes that created time savings of 11% and improved the returning customer rate by 5%.

Technical Review 426

Technical Review Budget Prince2 Software Review 426

LiquidPlanner

JANUARY 2, 2018

The updated PRINCE2 guidelines that were released this year also include information on tailoring for your environment. Industries like construction, software engineering, and consultancy probably see this as less of an issue. But for everyone else, resource management in knowledge work is a huge problem.

2018 106

2018 Certification 2011 Prince2 106

Epicflow Blog

SEPTEMBER 19, 2022

The second dimension represents the maturity levels based on the Capability Maturity Model developed by the Software Engineering Institute (one of the most popular and widely-accepted models of organizational maturity assessment). Let’s take a look at these levels. . Level #1: Initial process.

Underperforming Technical Team 52

Underperforming Technical Team Prince2 Risk Management Software Engineering 52

Epicflow Blog

MAY 14, 2019

Facts and Fallacies of Software Engineering by Robert L. Great Planning Disasters by Peter Hall (University of California Press, 1982), recommended by Sean Doull-Connolly , a Senior Process Engineer at TIAA. DIscussion in PRINCE2 & MSP – Project & Programme Management + Agile Scrum.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

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. Software Engineering Institute, January 1996. México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46

2003 2014 2015 2011 46

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