The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Review software standards
|
|
Ensure that stakeholders have an understanding of the organisationalrequirements Completed |
Evidence:
|
Document softwarestandards according to projectstandards Completed |
Evidence:
|
Review implementation standards
|
|
Assign software standards to functions according to detailed technical plan Completed |
Evidence:
|
Take action to ensure that communication and distribution strategies are clear, coherent and meet overall project plan requirements Completed |
Evidence:
|
Monitor and report on implementation of standards against acceptance criteria and detailed technical specifications Completed |
Evidence:
|
Review software metrics and milestones
|
|
Define metrics in relation to the project milestones, and timeframe and cost considerations Completed |
Evidence:
|
Develop schedule of quality reviews Completed |
Evidence:
|
Determine quality considerations by identifying in-process measurement points that relate to critical organisationalrequirements Completed |
Evidence:
|
Determine method to benchmark and scale achievement against stated stakeholders requirements and cost considerations Completed |
Evidence:
|
Report metrics and milestones to stakeholders in a clear and coherent manner and take action to ensure written agreement Completed |
Evidence:
|