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

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

PM Basics

MAY 16, 2022

Below you’ll find a full guide on how to become a software PM. TL;DR: The steps to becoming a software project manager. Develop technical proficiency. Develop your interview skills. That’s an overall approach that will make you a software project manager. You need to develop curiosity in regard to new technologies.

Software Review 59

Software Review Technical Review Software Leadership 59

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 85

Software Review Technical Review Software Engineering Underperforming Technical Team 85

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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

Epicflow Blog

MAY 14, 2019

We all dream of reaching maximum success with our teams and projects, even though project failure is common. Create a Solid Project Plan and Clear Business Case. Creating a clear business case and a critical path that designs your plans can help you plan well.

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

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. 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.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

AUGUST 27, 2017

It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. The original post, while likely well meaning, coming from direct experience, focuses on ME the developer.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

MPUG

MAY 14, 2021

Please send those over at any time using the chat question box on the “go to webinar” control panel where we do plan to answer those questions for you throughout the session today. By education and training, I’m actually a software developer. Kyle: Do you have any questions during today’s presentation?

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

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

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 83

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 83

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

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. We use Vitech's Core.

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. The Design Structure Matrix (DSM) method, was introduced by Steward in for task-based system modeling and initially used for planning issues. It can be used to identify appropriate teams, work groups, and a sequence of how the tasks can be arranged.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

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

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

Herding Cats

JUNE 7, 2018

This makes no sense for any development project beyond a de minimis project. The Design Structure Matrix (DSM) method, was introduced by Steward in for task-based system modeling and initially used for planning issues. It can be used to identify appropriate teams, work groups, and a sequence of how the tasks can be arranged.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

MPUG

MAY 6, 2021

We do plan to answer your questions throughout the session today. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering.

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. These activities, their releationships and values are defined in a PLAN for increasing the probability of success for the project.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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. Covers every aspect of project management, from the responsibilities of project managers to planning and executing the project itself.

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”. Since all project work contains uncertainty, reducing this uncertainty - which reduces risk - is the role of the project team and their management. Either the team itself, the Project or Program Manager, or on larger programs the Risk Management owner. .

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. The Cone IS the Planned reduction of uncertainty as the project proceeds.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. The Cone IS the Planned reduction of uncertainty as the project proceeds.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Leading Agile

AUGUST 20, 2018

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. Try installing a typical business application on a pristine development environment. Requirements & validation.

Software Review 57

Software Review Software Technical Review Development Team Review 57

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. The notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Teamweek

NOVEMBER 4, 2022

Interview coding challenges are critical when hiring new software developers. Finding the right developer can be a difficult process. What are Interview Coding Challenges for Developers? These are technical quiz-type tests that require the developer to pick the correct answer out of several possible answers.

Software Review 94

Software Review Underperforming Technical Team Development Team Review Technical Review 94