Return to HomePage

---

Authoring

* Do have great authors spend more time creating, less time mentoring/reviewing.
* Do write guidance that has the right amount of detail for intermediate users
* Don't specify technology and version for core principles/guidelines.
* Do specificy Web application, Desktop Application, Web Services, or Component for core principles/guidelines

Releases

* Don't do releases on Fridays
* Do release on Wednesday's
* Do use Monday's build for Wed release
* Do drive the feature schedule through the Wiki
* Do spend some time at start of each release cycle to understand new feature design
* Do have an owner for release to improve the process

Testing

* Do have all team members use the daily build
* Do test every checkin
* Developer test changes before checking in for both regressions and to ensure any new functionality is working
* Another member of the team smoke tests each checkin after it is in. Rotate duty so noone is stuck with it every time.
* Do use regression test cases

Wiki Pages

* Do spell out a great name in the link
* Do spell out the full name in the title/heading
* Don't over-complicate page names
* Do leverage simple page naming conventions such as prefix or suffix for types
* Do deal with collisions as you need to by tacking on a 1 or 2 or whatever (in other words, don't try to avoid collisions through a heavy titling approach)

General

*
*
*

---

Return to HomePage