standard work in software development less 2011 11-01

Standard work in software development

Håkan Forss

hakan.forss@avegagroup.se - @hakanforss

”We are what we repeatedly do. Excellence, then, is not an act, but a habit.”

- Aristotle

http://www.tft.ucla.edu/calendar/academic/aristotle-conferance/

“Where there is no Standard there can be no Kaizen”- Taiichi Ohno

http://www.lean.org/FuseTalk/Forum/Attachments/TPS%20House%20-%20v2.gif

http://www.filmforum.se/recensioner/blu-ray/moderna-tider-1.476152.html

http://www.boozemovies.com/2010/03/review-face-on-bar-room-floor-1914.html

41 0001 224

32 261

Dropped 1/3

OUR STANDARD WORK

“To improve is to change; to be perfect is to change often.”- Winston Churchill

Done

• Set label in source control, ask CM to build the code, inform test

• Set status Resolved in TFS on the work item• Update time spent• Set status Resolved in TFS for work package

From development/functional tests Code check-in

Code follows defined code standards and architecture Code review done Database project updated

Changes are documented

Run test cases All functional tests are green All automated tests are green For bugs

Run test in DST with tester

Document dependencies in specification document Update TFS

Document all changes in the description field Set State/Reason to Awaiting deployment /Fixed Create Label Set test lead as [assigned to]

Let CM know that code is ready to be deployed to test

From development/functional tests → Ready for deployment to System test

Code check-in Code follows defined code standards and architecture

Code review done Database project updated

Changes are documented

PEBBatch Script updated Run test cases

All functional tests are green All automated tests are green Run test in DST

Document dependencies in specification document Update TFS

Document all changes in the description field Set State/Reason tol Awaiting deployment /Fixed Create Label Set test lead as [assigned to]

Let CM know that code is ready to be deployed to test

Standard work inSoftware development

Be explicit and brief

Use a physical list

Describe what you are actually doing,not what you would like to do

Should be continuously updated, by the team

Håkan ForssMail: hakan.forss@avegagroup.seTwitter: @hakanforssBlog: http://hakanforss.wordpress.com/

Books