Guidance
Home Phases Disciplines Milestones Roles Deliverables Guidance Help

The term guidance is used to represent the standards, guidelines, and procedures which IT professionals follow in their daily jobs.  Our guidance (note: you need to tailor this page) pertains to:

• Coding
• Configuration Management
• Modeling
• User Interface Development

Coding Guidance

• Visit the Coding Guidelines page

Configuration Management

Your organization should define:

• A standard/suggested folder/directory structure
• A version numbering scheme (this is often driven by your tool)
• A "how to" guide for CM

Modeling Guidance

• Visit the Agile Modeling Style Guidelines page.
• You might want to consider purchasing The Elements of UML 2.0 Style for anyone who models.  It is a pocket-book sized manual describing style guidelines for all 13 UML 2

User Interface Development

• User Interface Design Tips, Techniques, and Principles  
• User Interface Prototyping Tips and Techniques

Tips for Writing Good Guidance

1. Keep it concise, simple, and straightforward: nobody is going to read a 100 page coding standards document, they MIGHT read a 5-page one.
2. Base it on actual, good practice, not academic theory of the ideal way you want it to be.
3. People need to respect and agree to it, otherwise they won't follow it.
4. The best people to write guidance are the practitioners who are expected to follow it.
   

Page last updated: September 25, 2005 This page is tailored with permission from Ambysoft Inc.'s Agile UP Product Original page is Copyright © 2005 Ambysoft Inc.