Bijan Javidi, Senior Principal Consultant at Microsoft, held a two-day Trainer the Trainer (TTT) event in Augsburg for the GLS Development Process Best Practice training. In the audience: Alexander Zeitler, Peter Koen (soon to be Softie), Bernhard Spuida, Hannes Preishuber, Achim Oellers and others (no specific order, just to name a few).

As rehashing the entire two days would be a tad lengthy, I only pick two items that are important to understand why anyone would attend such a training:

• Why Development Process?
• Definition of Development Process Best Practice

Let's start with "Why Development Process?"

• Make development
  • Predictable
  • Repeatable
  • Manageable
• Reduce costs
• Streamline application construction
• Establish standards
• Reduces risk in .NET projects

After those incentives to have a process at all, let's dig into what DPBP is - here is the definition:

• Process based development methodology
  • Ultra light-weight, pragmatic and prescriptive
  • End-2-end development process model
    • From requirements to deployment
• Minimum set of documents
  • Small number compared to UP
• Step-by-step guideline
  • How to create these documents
• Uses Office and Visio formats (UML)
  • DOC, XLS, and VSD templates
• DPBP is agile
  • Leverages many XP features
• End of prose text in development process
  • Minimizes text
  • Uses structured information
• Lazy modeling
  • Model only if you have to
    • Architecture metaphor (XP)
  • Uses minimum of everything to do the job

Bascically we are talking initialization, analysis, design, implementation and deployment. And that was then the contents of the two-day workshop in Augsburg.

Networking was commenced at the evening event on Monday, in the Welser Kuche with a medieval meal:

Want see more fotos? Look no further (German titles and description though)