PM Basics

JULY 1, 2020

For sure, the easiest way to become a software project manager is by getting a promotion inside an IT company. So, if you are just starting your career, I strongly recommend getting a job on an IT project in any other capacity like QA, Developer, DevOps, Business Analyst, or a Scrum Master. 10 to 15 people on the project team.

Software Review 98

Software Review Technical Review Underperforming Technical Team Leadership 98

Herding Cats

JUNE 12, 2018

This is simply good process development and management. This, of course, is simply poor process improvement and a fallacy since without the root cause the symptom cannot be fixed and will return. At a minimum, at the end of every week, a Scrum team assess physical percent complete at the end of the Sprint. Standish Number.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . 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.

Estimate 64

Estimate 2006 2005 2013 64

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

Leading Agile

FEBRUARY 12, 2024

Today, we take a look at why your software isn’t soft, explore the challenges of writing code at scale, and discuss a modern approach to writing code that will maintain its safety and simplicity over time. Video Transcript Chris Beale In traditional software development. There’s this idea of test driven development.

Software 71

Software Underperforming Technical Team Governance Government 71

Leading Agile

OCTOBER 17, 2018

We’ve had a bad habit at our house over the years. The connection with software development/maintenance is probably obvious. Tying Up Loose Ends in Software. Keeping code clean at all times really ought to be considered baseline job performance for a software engineer. Tying Up Loose Ends at Home.

Software Review 83

Software Review Technical Review Software Engineering Underperforming Technical Team 83

Epicflow Blog

MAY 14, 2019

We all dream of reaching maximum success with our teams and projects, even though project failure is common. Business drivers have to be translated into project drivers by a strong technical team, not management. Perform Risk Management. Read more: How to Ensure Project Success: Risk Management Matters.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

JUNE 12, 2018

This is simply good process development and business management. This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return. The notion of waterfall development on slide 9 as actually prohibited in our domain. Have you done a Root Cause Analysis?

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Leading Agile

JUNE 18, 2018

I remember joining a team in the late 1970s that supported an application used worldwide by a large corporation. The team resolved to drive that number down. It’s amusing until one reflects on the potential consequences when a large proportion of software we depend on for everyday life is of this quality.

Software Review 81

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 81

MPUG

MAY 14, 2021

By education and training, I’m actually a software developer. There was another study done that shows that 122 million wasted for every $1 billion invested due to poor project performance, a 12% increase over the previous years. I got junior software engineers, software engineers, senior software engineers.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

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. We develop these reference classes using Agile Function Points.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JUNE 7, 2018

This makes no sense for any development project beyond a de minimis project. It can be used to identify appropriate teams, work groups, and a sequence of how the tasks can be arranged. Risk interaction within systems and subsystems, between functional and physical elements, can also be modeled with DSM. No interconnections.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

FEBRUARY 9, 2018

If, for example, a project manager believes a member of his or her team is a fast and effective worker, each time that team member works fast and effectively or is told by a colleague about the work that has been done fast and effectively, the project manager will consider his or her belief to be well-founded. What To Do Next?

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

AUGUST 27, 2017

The original post, while likely well meaning, coming from direct experience, focuses on ME the developer. And like many posts and tweets about estimating, it's made from this point of view, not the business point view, not from the point of view of those paying the developer. This Value is developed during the Product Planning session.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

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.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JUNE 7, 2018

This makes no sense for any development project beyond a de minimis project. It can be used to identify appropriate teams, work groups, and a sequence of how the tasks can be arranged. Risk interaction within systems and subsystems, between functional and physical elements, can also be modeled with DSM. No interconnections.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

Herding Cats

MAY 8, 2016

Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. Before listening to any conjecture that estimates aren't needed to make decisions in the presence of Uncertainty for software development, please read these books. What are we looking for? Reading Materials.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Wrike

MARCH 4, 2015

So while you want to learn more about project management — either to pick up new skills or sharpen the ones you’ve already developed — you don’t have unlimited hours to read every book on the subject. Strategic Project Management Made Simple: Practical Tools for Leaders and Teams – Terry Schmidt.

Software Review 53

Software Review Underperforming Technical Team Technical Review Software Developers 53

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create risk to the success of the project. Since all project work contains uncertainty, reducing this uncertainty - which reduces risk - is the role of the project team and their management. Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

MPUG

MAY 6, 2021

He is responsible for the implementation of enterprise project management solutions for Edwards’ clients as well as overseeing the custom application development performed at Edwards around enterprise solutions and Microsoft Project for both desktop and server as well as SharePoint. What does the team care about?

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. Uncertainty creates Risk. Risk management requires active reduction of risk. This extended post covers.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Leading Agile

AUGUST 20, 2018

But there’s a risk that people will get excited about automation and get ahead of themselves. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. First, there’s a tool-centric mentality about software-related work.

Software Review 55

Software Review Software Technical Review Development Team Review 55

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28