Wrike

AUGUST 5, 2020

When it comes to risk management , a risk breakdown structure is a powerful tool in a project manager’s toolkit. According to the Project Management Institute (PMI), a project risk is defined as “an uncertain event that, if it occurred, has an effect on at least one project objective.” . Source: Fool.com ).

Risk 41

Risk 2002 2003 PMI 41

Herding Cats

MARCH 17, 2019

Business, Technical, Systems, Risk, and Project Management. Managment Processes. Nine Best Practices of Project Management , Software Program Managers Network (SPMN). Top Habits of Successful Project Managers. The Nine "I's" of Program Success ," College of Performance Management.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

JULY 8, 2018

This advocate continually confuses Macroeconomics of financial markets and sovereign finance with Microeconomics of software development. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty. Pich, Christoph H.

2002 34

2002 2008 Technical Review Software Review 34

International Institute for Learning

SEPTEMBER 20, 2022

According to a common and general definition, Team Management can be seen as the ability of an individual (manager) or of an organization to lead a group of people to accomplishing a task or common goal. Good management of a team means to do the best by and for the employees. By Luigi Morsa.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Herding Cats

MARCH 11, 2017

Uncertainty is related to three aspects of the management of projects: The external world - the activities of the project itself. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. One starting point is the value at risk.

2003 46

2003 2014 2015 2011 46

Epicflow Blog

MAY 14, 2019

Andrew Middleton , the Managing Director at AMWireless, tells us how to make sure you aren’t fighting a losing battle by trying to manage the unmanageable: “All project stakeholders have got to be on board right from the start and it’s up to the PM to make sure it stays that way! Perform Risk Management.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

JULY 8, 2018

This advocate continually confuses Macroeconomics of financial markets and sovereign finance with Microeconomics of software development. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty. Pich, Christoph H.

2002 28

2002 2008 Technical Review Software Review 28

Herding Cats

OCTOBER 5, 2018

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 ? The program management processes should seek to reduce uncertainty in the variable of the project. Steve McConnell. 1, January 2011.

2012 48

2012 2007 2011 2010 48

Herding Cats

APRIL 13, 2018

Traditional methods of quantitative cost-benefit analysis, like Net Present Value (NPV) or Discounted Cash Flow (DCF), either ignore or cannot properly capture the needs of management for flexibility to adapt and revise later decisions based on the uncertainties found on all IT projects. IT Risk Management. Here's a sample.

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Better Sure than Safe?

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Management Processes (#MP). Project Performance Management (#PPM). Agile Project Management (#APM). Risk Management (#RM). Cost, Schedule, and Technical Performance Management (#CSTPM). Management Processes.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MAY 7, 2019

The reason for this resource page is the lack of understanding of how to estimate, the urban myths about software estimating, and the fallacies that estimating is not needed, when developing software, in the presence of uncertainty, when spending other peoples money. Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc.

Estimate 40

Estimate Software Review Software 2012 40

Planio

JULY 22, 2020

The number one thing every project manager needs to level up their skills is experience. A good project management book. While there are tons of fantastic resources online for learning how to be a better project manager (such as this blog!) Jump to a section: The best books for mastering the fundamentals of project management.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Workzone

JULY 18, 2022

As of January 2022, there are over 450 project management software solutions on the market, according to Software Advice ! With so many choices available, you’re likely wondering which software is right for your team. With so many choices available, you’re likely wondering which software is right for your team.

Software Review 26

Software Review Underperforming Technical Team 2022 Software 26

Workzone

APRIL 23, 2020

There are over 400 project management software solutions on the market, as of April 2020, according to Software Advice. With so many choices available, you’re likely wondering which software is right for your team. With so many choices available, you’re likely wondering which software is right for your team.

Software Review 26

Software Review Underperforming Technical Team Software Technical Review 26

Leading Agile

FEBRUARY 11, 2019

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? What is needed is a Product Manager responsible for the business value of the product. What has changed?

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

Leading Agile

JUNE 18, 2018

Here are some things for managers, programmers, and testers to keep in mind. The most fundamental way to ensure high quality when developing new code or modifying existing code is to learn and use generally-accepted good software design principles. There will be plenty of issues to deal with that we can’t control.

Software Review 101

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 101

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. Building software. Preparing test data to exercise applications prior to deployment.

Software Review 78

Software Review Software Technical Review Development Team Review 78