SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 3 of 3
  1. #1
    Member
    Join Date
    Feb 2002
    Location
    Toronto, Canada, ON
    Posts
    54
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    CMMI for small projects/work orders

    Hello,

    Our company is moving towards CMMI Level 3 and we are trying to define the Tailoring Options for small projects. We have work orders/small projects that are equal in effort to 10 - 20 days in total (smetimes more than that up to 2 months). Since following the CMMI Level 3 processes require whole set of documentation followed it becomes inpractical and time-consuming to assign a huge effort to creating documentation.

    Could you please advise on what approach should be taken to reduce amount of hours spent on documentation, what documetation could be altered, and yet to ensure that the process is followed?

    Thanks a lot.
    Kina

  2. #2
    Member
    Join Date
    Feb 2007
    Location
    Virginia, USA
    Posts
    238
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: CMMI for small projects/work orders

    My company has a minimum man-hour threshold and we waive a number of processes for projects which we believe will be below that threshold.
    -Troy
    Do or do not... there is no try. -Yoda

  3. #3
    Member
    Join Date
    May 2008
    Location
    Brisbane
    Posts
    67
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: CMMI for small projects/work orders

    Righto
    In my hunble opinion, this is the problem with methodologies, they're just awesome for project level deliverables, but scaling (in this context, the ability to scale down is frequently overlooked).

    Anyway, some practical advice would be:
    1. Instead of full blown documents, where the frist 15 pages are project preamble and 'cut n paste', just create sections within a single document to represent the lifecycle methodology you use.
    2. Example, define, design, build, test, implement are sections within a single document not a seperate document for each. Oversimplified? Probably, but the effect is to maintain and audit trail of the changes.
    3. Typically BAU streams of work or discrete peices of functionality and are part of a maintenance release which are 20% enhanced functionality and 80% regression.

    Hope some of this is useful to you.
    Good luck
    Cheers
    Chris


    Test with the heart of a purist. Analyse with the mind of a pragmatist.
    http://jetstream07.blogspot.com/

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 10.71%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 03:37 AM.

Copyright BetaSoft Inc.