Loading...
 

Files from Authors other than Gilb

Downloads: Books, Manuscripts, Papers, Articles, Case Studies, Course Slides, Case Tools, etc. submitted by Gilb. Not written by Gilb.
  File Galleries  > Files from Authors other than Gilb
  T Filename Name Description Created / Uploaded Last modified Uploaded by Creator Hits
JacobsCa.pdf Introducing Measurable Quality Requirements (Planguage at Ericsson Germany Research report) Introducing Measurable Quality Requirements: A Case Study
Stephan Jacobs Ericsson Eurolab Deutschland [email protected]		 Tom Gilb Stephan Jacobs 85
bronson hp evo thesis-v3.pdf Best Practices for Evolutionary Software Development by Darren Bronson A MBA/MSC study of Gilb's Evo at HP for MIT Best Practices for
Evolutionary Software Development
by
Darren Bronson

UPLOADED TO GILB.COM 15 JULY 2014

B. S. Computer Engineering, University of Illinois, 1992
M. S. Electrical Engineering, Stanford University, 1994

Submitted to the Sloan School of Management and the
Department of Electrical Engineering and Computer Science in partial fulfillment
of the requirements for the degrees of

Master of Business Administration
and
Master of Science in Electrical Engineering and Computer Science

in conjunction with the
Leaders for Manufacturing Program

At the
Massachusetts Institute of Technology
June 1999

See also the study available on this site
RAPID AND FLEXIBLE PRODUCT DEVELOPMENT: AN ANALYSIS OF SOFTWARE PROJECTS AT HEWLETT PACKARD AND AGILENT
by
Sharma Upadhyayula
M.S., Computer Engineering University of South Carolina, 1991
Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of
Master of Science in Engineering and Management
at the
Massachusetts Institute of Technology
January 2001

http://www.gilb.com/tiki-download_file.php?fileId=65



 Tom Gilb Tom Gilb 2168
Tse & Kahlon Presentation.pdf The principles and application of Planguage for Managing System Innovation SLIDES for SQM conference, BCS 54 Sept 2013, London
Paper at http://www.gilb.com/dl582
Great real pharmaceutical hospital case with real improvements.

by
Man-Chie Tse1,2 & Ravinder Singh Kahlon 1,2 {Man-Chie, Ravi}@dkode.co
1 dkode Limited, London, United Kingdom.
2 University of Ulster, Northern Ireland, United Kingdom.


 Tom Gilb Tom Gilb 2053
Tse & Kahlon Paper.doc The Principles and Application of Planguage for Managing Systems Innovation Man-Chie Tse1,2, Ravinder Singh Kahlon1,2


Management of systems innovation refers to managing the innovation process and the implementation of its results within an organisation context. In today’s dynamic and turbulent world, organisations face a serious challenge which is to either perish or revolutionise. Unless an organisation evolves and updates the ways services and products are delivered, a risk of being overtaken by competitors will be encountered.
Within the tradition of IT projects, engineering system design requirements purely focused on qualitative statements. Such statements are ambiguous and can lead to failures without ever making any impact. This paper aims to investigate the principles of Planguage, developed by Tom Gilb.
The objective of the paper considers the application of Planguage in order to determine meeting performance targets, resource cuts and increasing service demands in a healthcare systems innovation case study. The primary benefit is that the uptake of Planguage has the potential to reduce uncertainty and deliver significant efficiency savings effectively.
 Tom Gilb Tom Gilb 2303
Capers Jones Requirements2013.doc SOFTWARE REQUIREMENTS AND THE ETHICS OF SOFTWARE ENGINEERING Draft 6.0 July 9, 2012 Capers Jones Abstract

Software requirements are a weak link in the chain of software engineering technologies. Requirements are usually incomplete and change at rates in excess of 2% per calendar month. For many years one common definition of quality has been “conformance to requirements.” However this definition ignores the fact that some requirements are hazardous or “toxic” and should not be included in software applications. Since clients themselves may not realize the dangers of toxic requirements, software engineers have a professional and ethical responsibility to point out the hazards of dangerous requirements and ensure that they are safely eliminated.		 Tom Gilb Tom Gilb 4100
LONDON TALK XII JOHN GALL FINAL.pdf HOW TO USE CONSCIOUS PURPOSE WITHOUT WRECKING EVERYTHING HOW TO USE CONSCIOUS PURPOSE WITHOUT WRECKING EVERYTHING
By John Gall, MS, MD, FAAP
A talk prepared for presentation at the annual Gilbfest, London, UK, June 25, 2012		 Tom Gilb Tom Gilb 17638
EDUCATION2012.pdf Capers Jones, Education 2012 for Software Engineers including a proposal for a VirtualUniversity about 45 pages Tom Gilb Tom Gilb 3570
Building a Virtual Software Engineering University Capers Jones May 2012.docx Building a Virtual Software Engineering University Capers Jones Idea submitted May 7 2012 Tom Gilb Tom Gilb 2059
evolutionary path to defining processes for software products.pdf Dick Hollands paper on experiences with Gilbs methods as presented 5 April 2012 BCS Lean QA courses Tom Gilb Tom Gilb 4131
TG lean QA course 4-5-Apr-12.pptx Dick Hollands Slides for BCS Lean QA Course April 5 2012 see corresponding paper uploaded today Tom Gilb Tom Gilb 3264
rico11c.pdf Rico: Lean and Agile Project Management for Large Virtual Systems excellent half day slides , courtesy of Rico Tom Gilb 10409
Mays1990ExperiencesDefectPreventionIBMSysJ.pdf Mays et Al, Experiences with Defect Prevention Originally published IBM Systems Journal No. 1 1990
and as Chapter 17 of Gilb & Graham Software Inspection 1993
With Kind permission of the Author
DPP is the main basis for CMM Level 5 as designed by Mays colleague Ron Radice
I think this process is still valid and powerful, and have personally had amazing experiences with it at clients, like Boeing on aircraft engineering in the large. Tom Gilb		 Tom Gilb 6488
Book Chapter Published.rtfd.zip Book Chapter in MIcrofinance Book using Planguage Glad to inform you that my book chapter has been published just now. More details at the url below, mine is the first chapter and a copy is attached. I hope you would find time to go thro this and let me know your valuable feedback.

http://www.igi-global.com/bookstore/TitleDetails.aspx?TitleId=41740

You may recall our discussions about some parts of this paper last year, and you may recognize your own formulations as well. Many thanks for your guidance and encouragement, which has helped me in exploring some interesting areas. I have been looking at some aspects of development economics and find that while the use of metrics is widely prevalent, there is plenty of scope for the systematic application of the principles of quantification and systems engineering in these domains.

Best regards,

N.V.Krishna		 Tom Gilb 2792
CASE STUDY ATUSHI 2010 JaSST_2010_E3.doc Case Study Data: Sony Spec Quality Control "A Case study of Agile Inspection －Defects Density and Evaluation Criteria " A Case study of Agile Inspection
－Defects Density and Evaluation Criteria －
Copyright © 2010 by Nagata Atsushi†
†System Quality Department, B2B Solutions Business Group, Sony Corporation,
4-14-1 Asahi-cho, Atsugi-shi, Kanagawa, 243-0014 Japan
E-mail: †[email protected]

Abstract Agile Inspection is a document inspection process that has been proposed by Tom Gilb. The objective of this process is to improve software document quality. The process has iterative structure, Sampling -> Inspection -> Logging -> Judgment -> Rewrite. During iteration the document quality is improved, and when it reaches the Exit Criteria, we exit from iteration and proceed to the next process. The identifier of quality used is the unique number of defects per logical page (300 words/page). This is estimated by the number of defects found in inspection. The paper argues the effectiveness of Agile Inspection process by a case study.
Keyword Inspection，Review，iteration，agile, document quality
 Tom Gilb 3428
NTNUIT_Value-Management-Meetup_Oslo_Okt-2010.pdf NTNU-IT_Oslo Value Management Meetup LANGUAGE: Norwegian
SLIDES: EVO - Et virkemiddel for å kommunisere prosessforbedring		 Fjerdrumsmoen Arne Fjerdrumsmoen 3478
BERNTSEN HONEYWELL EVO CASE 2006 icspi presentation.pdf Jerry Berntsen, Honeywell, 2007 ICSPI Conference Slides Distributed Development Improvement with VPD™ and Iterative Development, An Experience Report Tom Gilb 7545
Jones Software Engineering Best Practices Book reusechapt2.doc Capers Jone: Best Practices for Software Reusability This is a recent book chapter from his book "Software Engineering Best Practices".

I think it is particularly strong in show the potential breadth of Reuse in software )not just code), and it gives us research data from industry to jolt us into realizing that this can be a very profitable investment - one of the best!


[http://books.google.com/books?id=CJd__8ANvtQC&printsec=frontcover&dq=capers+jones+software+engineering+best+practices&source=bl&ots=cb4zwv6Hbl&sig=G02K27mEaQ5C_UhBo35BYuD3pKs&hl=en&ei=7ehmS5WbIcvM-QaCya2VBw&sa=X&oi=book_result&ct=result&resnum=1&ved=0CAkQ6AEwAA#v=onepage&q=&f=false]		 102878 8845
Oslo-Value-Management-Meetup-Lean-Frode-Odegard.pdf A Multi-Dimensional Framework for Lean Transformations SLIDES: used by Frode Odegard to present Lean to Oslo Value Management Meetup. Email: [email protected] Kai Thomas Gilb Frode Odegard 4356
Cotton HP EVO Aug96 Evolutionary Fusion: A Customer-Oriented Incremental Life Cycle for Fusion PAPER. Hewlett-Packard Journal, August 1996, Vol. 47, No. 4, pages 25-38.
An excellent detailed view of the Evolutionary project management process as taught Corporate-Wide at HP. The author was on a project team at HP about 1990 which Gilb taught early versions of the Planguage method. See another member of that Project in MAY96.
[May 2003] , HP Corporate Engineering, Palo Alto. “Fusion Newsletter” Vol. 4.2 April 1996, Software Technology Lab, HP Labs, 1501 Page Mill Road, Palo Alto CA, USA-94304.

HP Journal Paper

Author: Todd Cotton, HP		 Tom Gilb 5032
Love Quantification Lawrence Day 2005.doc Love Quantified by Lawrence Day A Paper submitted in response to an academic challenge at the C-6 Residency which was attended in partial fulfillment of the degree of Doctor of Philosophy in Applied Management and Decision Sciences




Walden University
February 2005
 102878 5006
Evo i Confirmit - ROOTS 2009.pptx Johansen: 6 Years of Experience Evo Planguage SLIDES
Six Years of Experience in Managing Quality in an International Product: What Have We Learned?

A Gilb client, using Evo and Planguage to manage all product qualities. With amazing quantified improvements as a track record, and a company that is increasing business in 2009 and beating their competition on delivered quality aspects.
There are earlier reports in papers on theis website from Trond and Tom

This was held by invitation at ROOTS conference 29 April 2009 Bergen, Norway.		 Tom Gilb Trond Johansen 5964
Smidig utvikling er ikke i maal - av Trond Wingaard.pdf Smidig utvikling er ikke i mål Computerworld article in Norwegian by Trond Wingård - Steria.no - "Markedsføringen har virket, nå må vi slutte å evangelisere og heller ta fatt på utfordringene." "Vi trenger altså mer fokus på å definere mål og styre mot måloppnåelse" Kai Thomas Gilb Trond Wingård 4139
Chroust Motivational issues OK copyright motivprov_04a.pdf Motivation for Software Developers Chroust, G. and Hoyer, C., Motivational Issues in Creating
Reusable Software Artifacts, in:
R. Trappl (ed.) Cybernetics and Systems 2004, vol II, Proc. 17 EMCSR 2004, pp. 417-422 Austrian Soc.
für Cybernetic Studies, Vienna 2004.}}

I (Tom) like to say 'motivation is everything' - this excellent paper brings out the practical details for programmers and other developers. Tom

 Tom Gilb 5604
localization culture -Putnik-Gerard Chroust chr-$08b$.pdf Software Localization and Culture L
Localization, Culture, and Global
Communication
Gerhard Chroust
J. Kepler University Linz, Austria

An excellent insight, replete with good examples of the many problems of software localization.
With KInd Permission of the Author 2008 Proceedings Paper.

 Tom Gilb 4165
Jones Scoring Methods 2008.doc Jones, Capers: Scoring & Evaluating Sw Methods SCORING AND EVALUATING

SOFTWARE METHODS, PRACTICES, AND RESULTS

This is an explanation of the sources and means of evaluation that Capers Jones has used to build up the tables available on this website, and as the basis for his forthcoming book (2009)

It is a very thought provoking view of our software practices and you will want it as a tool next time the discussion starts about some of our methods!
Tom Gilb

Version 3.0

November 13, 2008

On the website with Permission from the Author

 Tom Gilb Jones, Capers 4413
Shriver Ryan Measurable Value with Agile in Feb 2009 Overload.pdf Ryan Shriver: Measurable Value with Agile Measurable Value with Agile
Are you solving the right problem or simply
solving the problem right? Ryan Shriver shows
us that both are needed for value delivery.

A great paper illustrating the use of Evo in a Scrum environment.


 Tom Gilb 4434
Jones Methods ratings version 2 Oct 24 08AverageScores.xls Jones, Capers: Sw Methods Effectiveness Rating This is a thought provoking rating of the effectiveness of a wide variety of well known software methods.
An earlier sort of these by frequency of use, concluded that the least effectives techniques, even harmful ones, are used the most!
XL spreadsheet Oct 24 2008		 Tom Gilb 3664
Measuring Business Value with Agile presentation_Oct2008.pdf Measuring Business Value with Agile presentation Slides: Presentation by Ryan Shriver.
Transforming Rhetoric into Reality
 Kai Thomas Gilb 4558
agile-benefits-1.xls Method ROI Data Rico Rather interesting data about return on methods!

Updated 12 Sept 2008

David F. Rico
7862 Crossbay Drive
Severn, MD 21144 USA

(H) 410-551-3813
(C) 410) 924-5210

Email: [email protected]


 Tom Gilb 3830
rico08b PAPER SEPT 08 AGILE VERSUS TRADITIONAL METHODS.pdf Rico Agile sept 08 excellent material Tom Gilb 11355
rico08c AGILE SLIDES SEPT 2008.pdf Rico Agile sept 08 excellent material Tom Gilb 4917
Radice Software Inspection IBM.pdf IBM INSPECTION PLUS TEST DATA CASE RADICE Ron Radice
Who invented CMM, has 2 books, one recent about Inspection, and who really co-invented Inspection with Fagan has written this case study and given us permission to shore it here.
I personally think it is a great and insightful paper about the professional and mature practice of using inspection and Test data to manage the bug levels of software.
More on Ron from his website www.stt.com

small pdf file.		 Tom Gilb 5996
Haskins-2008_Socio-technical-SE.pdf SYSTEMS ENGINEERING HASKINS PhD Using systems engineering to address socio-technical
global challenges

Cecilia Haskins, CSEP
NTNU, Trondheim, Norway
[email protected]

Copyright © 2008 by Cecilia Haskins. Accepted for presentation CSER08.

Abstract
The discipline of systems engineering continues to mature, but no systems engineer has
ever been awarded the Nobel Peace Prize, while economists, politicians and others are putting
more attention to the global socio-technical challenges that face the planet today. This paper
will explore the essence of the systems engineering discipline and suggest ways in which
systems engineering practitioners, researchers and educators can meet the global challenges.

Table 1 compares Planguage /Evo to several other systems engineering approaches, with reference to 38 subdisciplines (Planguage has 36 of the 38!)

 Tom Gilb 8696
Jones 21 July08 DefectRemoval2008-3.xls Defect Removal Ability Defect Removal Ability Statistics
By Capers Jones

"These tables rank both defect prevention and defect removal in order of % ability.

The four columns of data allow some interesting calculations. Any combination of defect prevention and removal activities can be quantified to show effort, schedule, removal efficiency, and latent defects still present at the end of the series.

Some off-table data such as application size, compensation levels, and defect potentials are needed to complete the picture.

However, it is now possible to show how to achieve essentially any desired level of cumulative removal ability and know what it costs and how long it will take.

There is some additional data available that shows the differential efficiency of each method against various kinds of defects, but this simple table gives a picture that is easier to understand."

"This version includes an evaluation of quality metrics. Not many people know that LOC metrics penalize high-level langauges and make requirements and design defects invisible. The cost per defect metric penalizes quality and makes the buggies software look cheapest. Both metrics return negative value."

Excel File 21 July 2008

[email protected]

 Tom Gilb 4287
rico-dissert-082907.pdf EFFECTS OF AGILE METHODS ON WEBSITE QUALITY FOR ELECTRONIC COMMERCE EFFECTS OF AGILE METHODS ON WEBSITE QUALITY FOR ELECTRONIC COMMERCE

David F. Rico

1.4 MB pdf,
with permission of the author
David Rico

David F. Rico
7862 Crossbay Drive
Severn, MD 21144 USA

(H) 410-551-3813
(C) 410) 924-5210

Email: [email protected]


(August 29, 2007)




Dissertation submitted to the faculty of the
Graduate School of Management and Technology
University of Maryland University College


in partial fulfillment of the requirements for the degree of


DOCTOR OF MANAGEMENT

(Information Technology)

Tom Gilb 7487
sone08.pdf AGILE PROJECT MANAGEMENT MAPPING AGILE PROJECT MANAGEMENT PRACTICES TO PROJECT
MANAGEMENT CHALLENGES IN SOFTWARE DEVELOPMENT

http://davidfrico.com/sone08.pdf
(updated version with signatures) July 8 2008



A Dissertation

Presented to the
Faculty of Argosy University/Washington DC
College of Business and Information Technology

in partial fulfillment of
The requirements for the degree of

Doctor of Business Administration



By


Saya Poyu Sone

June, 2008

1st draft, final version will appear about june. This is posted 2 May 2008 with permission.

The Author can be contacted at

work [email protected]
home [email protected]

David Rico says of this
3. I really like her dissertation on Agile Methods (which highlights her experience and intelligence):

a. She chose a very relevant topic.
b. It's well written and integrated from end-to-end.
c. Her writing style and analysis is very scholarly.
d. The development of the conceptual model is very scholarly.
e. The choice of research methodologies was exceptional.
f. The data collection and analysis is very well done and educational.
g. The summary and conclusions were done in a scholarly manner.

I hope you enjoy it as much as I did, and not only learn from her scholarly exposition, but the Agile project management lessons as well (for your current programs and projects) ...

 Tom Gilb 7442
rico08a AGILE ROI.pdf Agile ROI Rico The purpose of this paper is to investigate the
return-on-investment (ROI) of agile methods. Agile
methods are new product development processes for
creating software-based goods and services. Agile
methods are a lightweight alternative to traditional
methods based on sequential product development
processes created over the last four or five decades.
The use of traditional methods is theorized to result
in higher quality software products because of well-
documented customer requirements and products that
exhibit fewer problems over their life cycle. Agile
methods on the other hand are used to achieve higher
customer satisfaction and product quality through
rapid implementation and early market testing. The
ROI of agile methods is yet to be fully explored
because of their newness, while the ROI of traditional
methods is well-understood. Therefore, the purpose
of this paper is to investigate and summarize the
literature on the ROI of agile methods. These results
show that the use of agile methods results in
increased cost-effectiveness, productivity, quality,
cycle-time reduction, and customer satisfaction
ranging from 10% to 100%.

JUNE 6th 2008
with kind permission of the Author.
Original Source: http://davidfrico.com/rico08a.pdf

David F. Rico
7862 Crossbay Drive
Severn, MD 21144 USA

(H) 410-551-3813
(C) 410) 924-5210

Email: [email protected]

http://davidfrico.com/
 Tom Gilb 7109
Agile Thinkers_ Tom Gilb - an example from Jens ....pdf Evensen on Evo Experience This Norwegian Champion of Our Evo methods - adding Evo ideas to Scrum - tells of his experiences in a consultant company winning business with a superior customer friendly approach.

[http://www.agilethinkers.com/2008/05/tom-gilb---an-e.html]
source and comments and Ryan Shriver Interview etc.		 Tom Gilb 25002
Agile Thinkers_ Tom Gilb - an example from Ryan Shriver.pdf Ryan Shriver on Evo [http://www.agilethinkers.com/2008/06/tom-gilb---an-e.html] is source

Experience using Evo 2007-2008 interview		 Tom Gilb 4230
larman-iterative history and evidence-keynote.pdf Larman Iterative History Craig Larman's
Slides for the 2006 Agile Business Conference, London
On "History and Evidence of Iterative, Evolutionary and Agile versus the Waterfall "

with kind permission of the author
www.craiglarman.com

This is an exciting piece of research and presentation - notice how PERT Planning was misrepresented!		 Tom Gilb 6647
LinesofCode2008 may 10 2008 example.doc Jones LOC History Capers Jones

Lines of Code LOC History

May 9 2008		 Tom Gilb 21539
FunctPtBusModel2008 May 8.doc FUNCTION POINT USES A NEW BUSINESS MODEL FOR FUNCTION POINT METRICS

Updated May 8th (2010 Perspective)

Capers Jones

Version 7.0 May 7, 2008


Abstract

Function point metrics are the most accurate and effective metrics yet developed for performing software economic studies, quality studies, and value analysis. But normal function point analysis is slow and expensive. Function point analysis performed by a certified function point consultant proceeds at a rate between 400 and 600 function points per day. The cost per function point counted is around $6.00. Further, very small applications below about 15 function points in size cannot be counted. Function point analysis for applications larger than about 15,000 function points in size almost never occur because the costs and schedule are larger than most companies will fund.

 Tom Gilb 20894
Jones RiskMaster2008.doc Risk Master Prediction Tool Word, download
Describes Capers Jones CJonesIII at cs . com
Risk Master Tool

This tool allows extremely early prediction of project risks, perhaps in time to avert them. It can even estimate your legal costs!

 Tom Gilb 9097
Capers Jones 2008 Software EDUCATin 2008.doc HOW SOFTWARE PERSONNEL LEARN NEW SKILLS From Tom:
anybody in the business of teaching software people their trade, will be interested in this study of the 16 distribution channels for knowledge, and the changing knowledge transfer environment.


HOW SOFTWARE PERSONNEL LEARN NEW SKILLS

Version 9.1
March 19, 2008



Abstract

The rate of change of software technology is extremely rapid. New programming languages appear almost monthly. New programming tools appear almost daily. The fast rate of software technology change means that software professionals are faced with a continuing need to learn new skills. What channels are available to software professionals for learning new skills? How good are the available ways of learning, and what new ways are likely to occur?

For several years after the economic downturn of 2000 software educational opportunties were reduced. Attendance at conferences went down, some in-house training was cancelled, and some software instructors were laid off. By the end of 2005, educational opportunities began to increase again. By 2007 educational opportunities had once again expanded. However the apparent recession of 2008 is likely to affect several channels of education that utilize live instruction so educational offerings may decline.


Capers Jones, Chief Scientist Emeritus
Software Productivity Research LLC
EMail [email protected]

 Tom Gilb 8653
Change Agency for Requirements Engineers.pdf Change Agency for Requirements Engineers PDF version of slides from Intel that speaks about Evo, Planguage and Change of Culture

"To make sure you have this... It's a half-day shortened version of the 2-day internal class. Longer class covers more topics, but these are among the most powerful in getting real results. Since it's cleared for external, I can share it with you." < Erik Simmons Intel 17 April 2008		 Tom Gilb 4634
Matrix49 16April Version.xls US Sw Industry Statistics Capers Jones' remarkable collection of statistics about software, including lifetime, defect finding effectiveness, and dozens of other areas, by type of software, and size of software.
Capers Jones CJonesIII @ cs .com
for updates and permissions.

Quotations may be made with reference to the author. More extensive use, contact the author.

Placed on this site with CJ Permission April 15 2008		 Tom Gilb 4042
Chris Dale 2006 Business Case Deployment v3.ppt Business Performance Improvement using… Business Performance Improvement using… Gilb Methods + Goldratt’s Theory of Constraints & some other stuff.
Chris Dale (with Permission Dec 3 2007).

Value Driven Planning Seminar 2006
 Tom Gilb 4066
STATEOFART2008.doc Capers Jones: SOFTWARE ENGINEERING STATE OF THE ART 2007 Paper, Word, 25 Pages, Version November 21 2007.
Capers Jones: SOFTWARE ENGINEERING STATE OF THE ART 2007
The phrase “state of the art” refers to software development practices that have consistently yielded results that are in the top 15% of approximately 13,000 projects examined. There are hundreds of ways to develop software that lead to overruns and failures. Surprisingly, there are only a few ways to develop software that consistently result in successful outcomes.

The lists of causal factors are backed up by other sources from Jones such as his slides (see this website) and books (referenced).
 Tom Gilb 20763
SmartDecisions_v2.pdf Smart Decisions: Evo + Scrum "Smart Decisions
How to make them by aligning projects, agile teams and success with measurable business goals"

BY Ryan Shriver => [email protected]

Added with Permission from RS 23 Nov. 2007

PDF SET OF SLIDES FOR PRESENTATION MADE AT GILB LONDON SEMINAR 2007

Ryan shows how they added Evo to Scrum for better value delivery control.



 Tom Gilb 8891
QFD2 [email protected] Clausing.pdf QUALITY FUNCTION DEPLOYMENT (QFD) QUALITY FUNCTION DEPLOYMENT (QFD)
Listening to the Voice of the Customer.
Don Clausing , [email protected]
(with permission Nov 4 2007)
MIT ESD.33
This is an excellent and deep paper on QFD with examples from Toyota and Xerox.

This paper is referenced in my NOvember 4 2007 What is Wrong with QFD paper, on this website.

 Tom Gilb 18118
Ebert Requirements 2006 IEEE.ppt SLIDES: (Ebert ALCATEL Case)Understanding the Product Life Cycle: Four Key Requirements Engineering Techniques A field study
involving many
industry projects
revealed that only
those that took
a requirements
engineering
perspective in four
key product lifecycle
management
activities were
successful.

TOM GILB MADE THESE SLIDES AND WAS IMPRESSED BY THE PAPER.
IT HAS PARTICULAR INTEREST FOR PEOPLE STRUGGLING WITH MARKETING REQUIREMENTS AND UPSTREAM PRODUCT REQUIREMENTS		 Tom Gilb 5562
Thomson-Financial-byDickHolland.pdf Creating Real Business Advantage from Document Inspection and Winning at Pinball SLIDES. Author Dick Holland. Inspection Kai Thomas Gilb 5019
UNICOM.pdf Inspections: An Agent of Change PAPER. In 1994 Dick Holland and his group learned both Inspection, Defect Prevention Process, and Requirements Driven Management methods, in London from Kai and Tom Gilb. They produce software and services for the City investment market. Dick and his team did a great job of implementation of all of these methods. They turned business failure into business success by imaginative and persistent championing of these ideas. Dick is great at giving a lively and well illustrated presentation of the history. Plenty of facts, charts, quotes and conceptual big picture overview.
Primark Investment Management Services Limited.
"This is the story of a journey; or, rather, the beginning of a journey. It's a journey that we have embarked upon whilst its destination is but a vision - a vision of the future in which our product is recognised clearly as the best of its kind on every measurable scale."
This is a model client of ours, our students and professional friends, explaining their experiences using Inspection and quantification of business/technology objectives to serve their customers. Highly recommended reading.

Author: Dick Holland		 Kai Thomas Gilb 9126
HP SharmaUpadhyayulaHP Evo2000.pdf RAPID AND FLEXIBLE PRODUCT DEVELOPMENT: AN ANALYSIS OF SOFTWARE PROJECTS AT HEWLETT PACKARD AND AGILENT PAPER. Sharma Upadhyayula , M.S., Computer Engineering, University of South Carolina, 1991

THIS IS A SERIOUS SCIENTIFIC INDUSTRIAL STUDY OF THE GILB EVO METHODS AS USED BY HP AND AGILENT FROM 1988

Submitted to the System Design and Management Program in Partial Fulfillment
of the Requirements for the Degree of
Master of Science in Engineering and Management
at the
Massachusetts Institute of Technology
January 2001
Abstract
Before companies started competing on Internet time, most companies involved in software
product development carried out the different phases of the product development sequentially. If,
during the later stages of product development (ex: coding), the company came across new
information or the user needs changed then these changes would be incorporated into the next
version of the product otherwise risk shipping the product late. Rapid innovation in the
technological areas and the Internet has created very dynamic environment in all walks of life. In
this environment, the user needs are changing very rapidly resulting in new challenges for the
companies and its product development managers. They have to respond to the changing needs
of the users very quickly either with rapid product releases and/or incorporating the changes into
product under development. To achieve this, companies need a product development strategy
that allows them to incorporate changes at any stage in the product development without affecting
their time-to-market.
This thesis focuses on strategies for rapid and flexible software product development. This
research will study systematically the range of approaches that producers of software and
hardware use for product development.

Thesis Supervisor: Michael A. Cusumano
Sloan Management Review Distinguished Professor of Management 		Tom Gilb 4977
Larman evoaug603.pdf Gilb's Evo in Larmans IID for Managers Book Chapter 10 PAPER - BOOK CHAPTER. Gilb's Evo method compared to other Agile Methods (in other chapters of the book)

Evo (short for Evolutionary Project Management) is perhaps
the oldest IID method with a significant agile and adaptive quality,
first taking shape in the 1960s and then published in 1976.
Evo emphasizes:
❑ short iterations, with evolutionary delivery each iteration
❑ evolutionary requirements and design
❑ adaptive client-driven or value-driven planning
❑ quantifiable measurements of value and progress
❑ defining all quality requirements with numeric measures
❑ optional use of a language, Planguage, for specifications
OVERVIEW
❑ Classification of Evo.
❑ Workproducts, roles, and practices.
❑ Demonstrate Planguage for Evo specifications.
❑ Common mistakes, adoption and process mixtures,
strengths and weaknesses.		 Tom Gilb 5027
May Zimmer Evo HP96.pdf The Evolutionary Development Model for Software PAPER. by Elaine L. May and Barbara A. Zimmer
HP Journal August 1996

DESCRIBES USE OF GILB EVO AT HP

The traditional waterfall life cycle has been the mainstay for
software developers for many years. For software products that do
not change very much once they are specified, the waterfall model
is still viable. However, for software products that have their
feature sets redefined during development because of user
feedback and other factors, the traditional waterfall model is no
longer appropriate.
by Elaine L. May and Barbara A. Zimmer
Hewlett-Packard, like other organizations developing software products, is always looking for ways to improve its software
development processes. One software development method that has become quite popular at HP is called Evolutionary
Development, or EVO (see reference 1 and Article 3). EVO uses small, incremental product releases, frequent delivery to
users, and dynamic plans and processes. Although EVO is relatively simple in concept, its implementation at HP has
included both significant challenges and notable benefits. This paper begins with a brief discussion about the EVO method
and its benefits, then describes software projects at three HP divisions that have used EVO, and finally discusses critical
success factors and key lessons about EVO.
Tom Gilb 5631
Boehm Keynote Testing slides.pdf Boehm: Educating Students in Value Based Software Engineering SLIDES. http://db-itm.cba.hawaii.edu/cseet2006/Boehm%20Keynote.pdf
CSeet Keynote slides
April 19 2006

A very interesting critique of conventional software engineering, as not being Value Based!		 Tom Gilb 4445

Concept Search