2007 Lean Process Software Engineering 
The IIL Blog
JANUARY 24, 2024
ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. LEAN processes emerged in 1991, with the Agile Manifesto launched by a group of software engineers in 2001. As ITSM evolved, so did the ways of delivering Information Technology services.
ProjectManager.com
JULY 25, 2019
You can thank Marc Andreessen , the American entrepreneur, investor and software engineer, for the hyphenated phrase. Dan Olsen, an expert in product management and author of The Lean Product Playbook , has emphasized product-market fit as critical to the success of a start-up. What is Product-Market Fit?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Project Pulse Journal
APRIL 15, 2024
Understanding these top five Agile methodologies that are not Scrum Framework: Kanban, Extreme Programming (XP), Lean Software Development, Feature-Driven Development (FDD), and Dynamic Systems Development Method (DSDM) is crucial for any team or individual looking to implement Agile practices effectively.
Herding Cats
DECEMBER 16, 2017
Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Estimating Software Costs: Bringing Realism to Estimating , Second Edition, Capers Jones, 2007. Estimating Software-Intensive Systems: Projects, Products, and Processes , Richard Stutzke, Addison-Wesley, 2005.
Herding Cats
NOVEMBER 7, 2016
The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.
Herding Cats
MAY 7, 2019
So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.
Herding Cats
MAY 10, 2019
Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999.
Expert insights. Personalized for you.
78 
Let's personalize your content