2002 Closing Lean Software Development 
Herding Cats
MAY 10, 2019
IEEE Transactions on Software Engineering , Vol. 3, March 2002. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 11 November 2002. Project Risk Management: Lessons Learned from Software Development Environment,” Y.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MARCH 11, 2017
Accuracy - how close is the estimate to the actual value? So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date.
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? There is no single step directly from chaos to a smoothly-functioning lean/agile operation.
Planio
JULY 22, 2020
Closing: Formally closing the project and documenting lessons learned. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Closing the project and measuring success.
Leading Agile
JUNE 18, 2018
In a 2002 piece entitled The Law of Leaky Abstractions , Joel Spolsky observed that abstractions over any implementation can leak details of that implementation. Open/Closed. Some people just expect the systems they support to fail periodically, and the “fix” is nothing more than a restart. Contracts vs. Promises.
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. Two closely related conceptual errors appear to be quite common. First, there’s a tool-centric mentality about software-related work. The company wanted to automate their dispatching process.
Expert insights. Personalized for you.
38 
Let's personalize your content