Lightweight Ticket Process (LPD)



Introduction

This is a project to create some XHTML/CSS material to assist with the documentation of process. In particular it is designed to be simple so that it can be used in a project WiKi for software developers. Current process documentation presentation frameworks are much more heavyweigh, for instance OpenUP requires a dedicated composer. LPD will require vi, or any text or html editor -- in particular it should be editble from a WiKi page

Motivation

Example

Simple Example Change Process

Purpose and final outcomes: To provide simple support for a development change set

Rationale: Before a change is built and integrated it needs to be documented for engineering reasons

Entry gate: A change has been identified and will take less that 4 days of developer effort
Exit gate: The change passes all unit tests and has been integrated into the smoke build
Abnormal process stages or exit gates: Change can be marked obsolete by team leader or project manager (requires a brief description)

Stage nameRole responsibleDescriptionData Requirements on stage exit
DocumentationTeam LeaderGathering all required data
  • Name of affected application and subsystem
  • Description of need or reference to need
  • Description of solution or reference to solution
  • Risks/impacts/benefits/costs
  • Testing required (or reference to tests)
  • Schedule constraints
  • Other dependencies
Make ChangesDeveloper or AuthorNew revisions are created and tested
  • List of new revisions
  • Actual effort taken
  • Test results
Accept changesTeam LeaderChange is reviewed and acceptedComment

License

Creative Commons License
This content on this page is licensed under a Creative Commons Attribution-ShareAlike 2.5 License unless otherwise stated.


Page Information

  • 1 month ago [history]
  • View page source
  • You're not logged in
  • No tags yet learn more

Wiki Information

Recent PBwiki Blog Posts