Download Center
 |
to Dutch download |
|
Download Center
|
|
Adobe Acrobat reader
.pdf files can only be viewed with the Acrobat Reader program. You will probably have this program already in your computer. If not, you can download it free of charge from the Adobe website. Te get it: click the following link:
Link to Acrobat Reader (note: size is 5.2 Mb, so it may take some time)
Note on downloading Acrobat (.pdf) files.
It is advisable not to just click on the download link of a .pdf file. In that case you will see the file, but it will not get into your computer. It is better first to get the file on your harddisk. Then you can read, re-read and print it at will. Do this by clicking the right mouse button. Then select in the pop-up menu: "Save target/link as ..." Then choose a conveniet folder to save the file in. It will now be loaded into your computer.
|
Booklet and Presentations on Evolutionary Project Management Methods |
| Most recent versions of Evo materials Booklets
Great article by Ryan Shriver about the Evo Requirements and Design approach:
Tutorial/workshop handouts
Case Study:
ETA - Evo Task Administrator tool
|
||
Evolutionary Development Methods allow Software and Development Projects, Systems Engineering projects, and actually any project, to be successfully delivered on time easily in a 30% shorter time than usual. If you don't believe it, let me show you how you can do it! Based on the experience of coaching and teaching over 100 projects in 25+ organizations in the Netherlands, Belgium, Germany, India, Ireland, Japan, Romania, South Africa and the US, I am so sure that it will work also for you, that I use a no-cure no-pay guarantee.
(Software) developers systematically fail to manage projects within the constraints
of cost, schedule, functionality and quality. Solutions have been developed during
the past 40 years, with important results published already over 30 years ago. Still,
in practice not much has changed. The challenge is to find ways to catch the practical
essence of solutions and ways to get the developers to use these solutions.
In the booklets we show methods and techniques, which do enable developers
and management to successfully managing projects within the constraints of cost,
schedule, functionality and quality. These methods are taught and coached in actual
development projects with remarkable results.
While software development results were usually delivered late, the delays in other
disciplines (like hardware and mechanical development) seemed to be non-existent.
Now that we have taught Software Development to deliver Quality On Time (the right
things at the right time and within budget), the delays in the other disciplines
become exposed. The methods and techniques described in this booklet are obviously
not limited to just software development. For those projects where delivering Quality
On Time is important it is about time that we are going to apply the techniques
at the Systems Development level. Therefore the next target for Evolutionary Development
Methods will be Systems Engineering.
Note that the contents of the booklets describe ongoing developments. The methods
are being used by the author with various clients and are continuously being optimised
based on results found.
Other material on Evolutionary methods:
Read Tom Gilb's 10 Evo Principles: click here.
For more explanation about Evolutionary Development project organisation, see the Evo pages. This material is mostly covered by the booklets introduced above.
Slides introduction Cleanroom Software Engineering
Cleanroom software engineering is a combination of software processes which enable us making software with:
- Zero failures in field use
A defect level so low that the customer stays unaware of any defects- Short development cycles
If you follow and optimise the right processes, you are done faster: Quality is cheaper.- Long product life
If the design documentation is the basis of the design, rather than the code, maintenance (80% of the cost of many software projects!) is much easier, enabling a longer economical life of the product.These slides were prepared for an introduction about Cleanroom Software Engineering, presented at the Metrics study group of SPIder, the Dutch Software Process Improvement network, in January 2000. Almost all slides are in English. If you invite us to present this introduction in English, the remaining few Dutch slides will be translated.
Download slides van een introductie "Cleanroom Software Engineering" (.pdf 690 kb)
Spreadsheet "Cost of slipping defects"
Calculate the influence of PSP and Inspections on your defect costs. If this does not convince you, what else can we do?
Download spreadsheet "Cost of slipping defects" (.xls, 38 kb)
Schematic diagram "Sub-process" in development
Starting from the PERIF (Plan - Execute - Review - Inspect - Finish) concept of a development sub-process, a more detailed diagram was elaborated. In this diagram, the Inspection process is shown in detail (ref. Gilb, SP6). The optional "gate" concept (ref. Cooper, D1) is also added. Note that Inspection assesses whether the result of the sub-process meets the inspection rules and meets the exit criteria. Inspection does not judge the contents of the result (document), unless prescibed by the rules. The "gate" is a Go/Kill decision point "Should we continue this project?". To be able to decide this, the input to the gate-process should be an inspected workproduct.
Don't be alarmed by the seeming complexity of the sub-process. You thought you were only to do the anticipated activity? If you reflect carefully, you should admit that you will be doing a lot of the elements shown. More or less...
Download diagram "sub-process" in development (.pdf, 47 kb)
Slides of the "Quality On Time" workshop
The slides of the "Quality On Time" workshop are available in Acrobat (.pdf) format. Originally, these slides were a mixture of Dutch and English. They are now (July 2, 2000) translated into English completely. If you find any Dutch language remains, please let me know.
Download slides of the workshop "Quality On Time" (.zip, 708 kb > .pdf)
Slides of the TMCE2000 conference workshop
The slides of the introduction by Niels Malotaux on the workshop of the TU Delft TMCE2000 conference (Tools and methods of competitive engineering) are available in Acrobat (.pdf) format.
Download slides of the TMCE2000 workshop introduction (.pdf, 108 kb)
Slides of an introduction lecture about SPI at NASA
The NASA Process Inprovement Guidebook (NASA-GB-001-95, 750 kb, in .pdf format) provides an overview of the SPI activities at NASA, with a lot of experience included. You probably can learn a lot from it. Why invent the wheel over and over again? It is much smarter to learn from others and continue from there.
These slides were prepared for an introduction about the NASA process improvement activities, based on the Guidebook, presented at the Metrics study group of SPIder, the Dutch Software Process Improvement network, June 1999.
Download slides introduction "Software Process Improvement at NASA" (.pdf, 275 kb)
Download NASA Software Process Inprovement Guidebook (.pdf, 750 kb)
Forms voor SPI
Refer for a description of these SPI forms and for inspection forms to the forms page.
Download TimeLog1 (.pdf, 10kb)
Download TimeLog2 (.pdf, 28kb)
Download filled in example of TimeLog2 (.pdf, 60kb)
Download excel file with both forms, to adapt to your own taste (.xls, 36kb)
Download Tasksheet (.dot, 35kb)Download slides "Document Inspections" (.zip, 227 kb > .pdf)
Download slides "How to start Document Inspections" (.pdf, 235kb) as used at the SPIder plenary meeting in Utrecht, November 22, 2000.
More about Inspections: see "6 hour and 4 hour Inspection process".
|
CMM documents |
Order in CMM2
In the following document I have tried to get some order in
the CMM level 2 KPA's, as many issues of the KPA's are or seem similar. In the column at
the right each row is summarized. At the bottom of the page (or next page) all Activities
where "documented procedure" is mentioned are listed.
From this you can make your own analysis....
