Archive for the ‘ii. Administration’ Category.
17th April 2008, 09:34 am
Thanks to ohskylab of myBlogLog for finding this.
The “How to Report Bugs Effectively” by Simon Tatham, professional and free-software programmer describes a general procedures on how to report bugs effectively on the site and only key tips are listed here as follows:
- It doesn’t work.
- Show me.
- Show me how to show myself.
- Works for me. So what goes wrong?
- So then I tried . . .
- I think the tachyon modulation must be wrongly polarised.
- That’s funny, it did it a moment ago.
- So I loaded the disk on to my Windows . . .
Join QAST Practitioner Group and give comment(s) at:
http://daniloalsonado.com/qastforum/index.php?topic=49.0
11th April 2008, 01:49 pm
Poor quality statement can affect one’s behavior to provide project sponsor and client with easy access to quality requirements, solve problems that need to be solved, justify poor quality action and alignment, justify wasted time, and focus on things. Without any clear understanding and idea of what the quality statement are, that one can go in search of things that are broken and his/her goal becomes fixing them. The following are sample activities that one could take to identify and define clearly the desirable quality goals or targets with the project sponsor, client, and team members on a project:
- Obtaining resources. This includes reviewing project sponsor and client general requirements and supporting documents.
- Understand the quality needs and/or expectations of the project sponsor and client and input of team members in terms of quality on the project.
- Determine the desirable quality goals and targets that are consistent with the needs and expectations of the project sponsor and client and input of team members. This includes identifying all the deliverables to be produced, deciding how to best validate their quality, and setting quality criteria and defining quality standards for the deliverables.
- Define quality statement in ways meaningful to project sponsor, client, and team members.
- Make sure that quality statement is reviewed and accepted by the project sponsor and client. This includes gaining project sponsor and client agreement with quality statement and re-confirming quality statement with client when changes are approved.
Join QAST Practitioner Group and/or give comment(s) at:
http://daniloalsonado.com/qastforum/index.php?topic=21.0
