The Six Sigma community often speaks of new or changed requirements – there is even a metric called requirements volatility. Doing this graphically in a matrix makes it easier to see holes in the planned interviews and make the proper corrections. Then consider the types of participants to cover, for example expert users, new users and difficult-to-satisfy users. Segment the population into specific areas, e.g. The customer matrix helps plan and assure that the correct representatives are included in requirements gathering activities such as interviews and observations. The matrix contains three simple aspects: 1) what does the company need to know, 2) where will the company get the needed information and 3) how will the company get the information? The learning objective matrix keeps managers from drawing conclusions before the proper time in the life cycle. If project managers bypass this critical thought process, they often are forced to rework plans and deliverables during the life cycle causing disruption in the project. This is done early in the life cycle to discourage users from jumping to solutions based on current biases. The learning objective matrix can help identify, plan and document such needs. It is necessary to learn things beyond current knowledge and experiences whenever embarking on a new project. If these Six Sigma tools, approaches templates, etc., are good for Six Sigma projects, why not use them in day-to-day software development and IT processes? Learning Objectives During a Six Sigma symposium, speaker after speaker presented good information on Six Sigma concepts, tools and approaches to use when working on a Six Sigma project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |