Standard work in software development less 2011 11-01

5,043 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,043
On SlideShare
0
From Embeds
0
Number of Embeds
3,245
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • If feels quite reasonable to use standard work in manufacturing process that repeat the same work over and over.
  • how can Standard work be applied to software development?Every project, every software I write is unique, one of a kind! Otherwise I would just reuse what I have previously done.Software development is a craft, an act of design and divine inspiration.
  • So how about surgery?A study of 41 000 trauma patients in the state of Pennsylvania—just trauma patients—found that they had 1,224 different injury-related diagnosesin 32,261 unique combinations.Mapping out the proper steps for every case is not possible…AtulGawande - The Checklist Manifesto: How to Get Things Right
  • In 2007 and 2008, a WHO pilot study involving hospitals in eight cities around the globedemonstrated that the use of a simple surgical checklist, developed by WHO,can lower the incidence of surgery-related deaths and complications by one third during major operationsThere are 234 million operations performed globally each year.At least half a million deaths per year would be preventable with effective implementation of the WHO Surgical Safety Checklist worldwide.A surgical safety checklist has gone from a good idea recognized in a pilot study to a global standard of care, which already has saved many thousands of lives.http://www.who.int/patientsafety/safesurgery/checklist_saves_lives/en/index.html During the 18 months of the program, an estimated 1500 lives were saved in the US state of Michigan alone.http://www.who.int/bulletin/volumes/86/7/08-010708/en/… it is far from obvious that something as simple as a checklist could be of substantial help. We may admit that errors and oversights occur—even devastating ones. But we believe our jobs are too complicated to reduce to a checklist.AtulGawande - The Checklist Manifesto: How to Get Things Right
  • Standard work in software development less 2011 11-01

    1. 1. Standard work in software development Håkan Forss hakan.forss@avegagroup.se - @hakanforss
    2. 2. ”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/
    3. 3. “Where there is no Standard there can be no Kaizen” - Taiichi Ohno
    4. 4. http://www.lean.org/FuseTalk/Forum/Attachments/TPS%20House%20-%20v2.gif
    5. 5. http://www.filmforum.se/recensioner/blu-ray/moderna-tider-1.476152.html
    6. 6. http://www.boozemovies.com/2010/03/review-face-on-bar-room-floor-1914.html
    7. 7. Dropped 1/3
    8. 8. OUR STANDARD WORK
    9. 9. “To improve is to change; to be perfect is to change often.” - Winston Churchill
    10. 10. 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
    11. 11. 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
    12. 12. 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
    13. 13. Standard work in Software developmentBe explicit and briefUse a physical listDescribe what you are actually doing,not what you would like to doShould be continuously updated, by the team
    14. 14. Håkan ForssMail: hakan.forss@avegagroup.seTwitter: @hakanforssBlog: http://hakanforss.wordpress.com/
    15. 15. Books

    ×