|
|
T
|
Filename
|
Name
|
Description
|
Size
|
Created / Uploaded
|
Last modified
|
Uploaded by
|
Creator
|
Hits
|
|
|
|
|
MxEvo.pdf |
Evolutionary Project Management Methods |
Based on experience at introducing Evo at Philips in Belgium in 2001. Description of issues in projects and description of the Evo process that emerged after one year experimenting. |
352.29 KB |
|
|
nrm |
|
3168 |
|
|
|
|
Planguage-introduzione.pdf |
Introduzione a Planguage |
A short introduction to Planguage - in italian |
57.20 KB |
|
|
comai |
|
3879 |
|
|
|
|
2005_04_20_AVT_710.doc |
Zero Defects |
Commercial product development with over 10 years use and over 15000 operators but zero field reported software defects. |
56.00 KB |
|
|
robsab |
|
4026 |
|
|
|
|
Anforderungsvorlagen from Goetz 2008 German Planguage Templates.doc |
GERMAN Deutch Planguage Requirement Design Templates |
Compliments of our good friend
[email protected]
3 of the Competitive Engineering Templates translated to German |
54.50 KB |
|
|
Tom Gilb |
|
6926 |
|
|
|
|
AE_Architects_IE.xls |
Impact Estimate Table |
Excel spreadsheet that's well documented and ready to adapt to your project. This is contains examples for Performance, Response Time and Transactions per Second, so is easily adaptable by architects and requirements engineers. This accompanies my Agile Engineering talks, for more information see theagileengineer.com. |
81.00 KB |
|
|
Ryan Shriver |
|
3025 |
|
|
|
|
The Beginning of the End Defining Project Closure.doc |
The Beginning of the End: Defining Project Closure |
How do you know when your part of the development race is over? Learn how to establish a clear finish line for your project. |
37.50 KB |
|
|
ExecutiveBrief |
|
5374 |
|
|
|
|
HelpQA.pdf |
Help! We have a QA Problem! |
How Evolutionary Planning techniques immediately helped a tester to become more than twice as productive, solving a backlog of half a year of work in 9 weeks. |
144.22 KB |
|
|
nrm |
Niels Malotaux |
3568 |
|
|
|
|
EvoRisk.pdf |
Controlling Project Risk by Design |
How the Evolutionary Project Management approach handles Risk by design. |
590.64 KB |
|
|
nrm |
|
4813 |
|
|
|
|
TimeLine.pdf |
TimeLine: Getting and Keeping Control over your Project |
How to estimate what you can deliver at a certain time (and what not) and what to do if what you think you have to deliver doesn't fit the available time. Deceptive options and real options. Last version at www.malotaux.nl/nrm/pdf/TimeLine.pdf . |
302.88 KB |
|
|
nrm |
|
2753 |
|
|
|
|
EvoTesting.pdf |
Optimizing the Contribution of Testing to Project Success |
How to extend the Evo concepts to the Testing and Quality Assurance processes. |
193.19 KB |
|
|
nrm |
|
2642 |
|
|
|
|
house-inspection sievers 2011.pdf |
Use of the Inspection Method in Building a House by Joerg Sievers |
Joerg Sievers
submitted Jlu 23 2011 |
100.39 KB |
|
|
102878 |
|
2529 |
|
|
|
|
MalotauxApcose2008.pdf |
Recognizing and Understanding Human Behavior to Improve Systems Engineering Results |
Many systems fail because engineers ignored, forgot to include, or incorrectly assumed how people actually behave. |
111.03 KB |
|
|
nrm |
Niels Malotaux |
7313 |
|
|
|
|
SHRIVER AGILE ENGINEERING FOR ARCHITECTS 2008 AE_ADC_2008.pdf |
Agile Engineering for Architects |
pdf of slides.
Become a systems engineer, not just a programmer!
Ryan Shriver > Managing Consultant
Focus here is on using Planguage for Design specification and evaluation.
[email protected]
Download this presentation at theagileengineer.com
|
1.84 MB |
|
|
Tom Gilb |
|
3819 |
|
|
|
|
Agile2009ResultIsAllThatCounts.ppt |
Agile2009: The Result Is All That Counts |
Presentation at the Agile Holland Conference 2009. |
1.95 MB |
|
|
nrm |
Niels Malotaux |
4036 |
|
|
|
|
EvoPlanning.pdf |
Evolutionary Planning or How to Achieve the Most Important Requirement |
Rewrite of the TimeLine booklet. Extra emphasis one what we can do if we find that, assuming working the way we currently are working, we won't make the project result on time. |
472.54 KB |
|
|
nrm |
Niels Malotaux |
3598 |
|
;){kind=link}