How apt amend the quality of the project team 2

How to amend the quality of the project team? (Rpm)
1. your team to use source code management tool that?
should be used. VSS, CVS, PVCS, ClearCase, CCC / Harvest, FireFly can. My alternative is VSS.
2. your project team using the defect management system that?
should be used. ClearQuest too complicated, my recommendation is BugZilla.
3. you still use Word to write the test group test it? Do not use Word to write
test (Test Case). Should be a devoted system, which can be Test Manager, you can develop one ASP.NET their own small websites. The cardinal intention is to Track and Browse.
4. Your team has not established a portal?
to have a entry to let Contact Info, Baselined Schedule, News and more. Recommended Sharepoint Portal Server 2003 to achieve 15 minutes to get. Can not supply to purchase SPS 2003 WSS (Windows Sharepoint Service).
5. your team with the best tools you can buy it?
should make a good tool to work. For example, should be secondhand VS.NET instead of Notepad to write C #. Procedures are normally fair use Notepad to write a show off. But it should also take into list the funds, so that is
6. your programmers work in a quiet environment it?
need a silence surroundings. This is exceedingly momentous, merely also to ensure that everybody over a certain area of ​​space.
7. your staff that everyone has a call it?
need a phone per person. And tel with voicemail function is best. Of course, on such a phone system with information overhead is not small. But at least one phone per person have, do not do a stand up was constantly shouted:
8. each one of you whom know thata problem should it?
should know. Feature at least anybody 1 should have a Owner,GHD Purple Butterfly 2011, of way, Owner can continue to Dispatch to others.
9. Have you ever had someone say,GHD MK4 Pure Straighteners,
to eradicate, Never suppose everything.
10. your team all the people all sitting around it?
absences. I disapprove the Virtual Team,GHD Purple Straighteners, likewise contrary Dev in the United States, Test Development in China this way. Could sit attach sit together aboard the best, the benefits of a quite, very much.
11. Does your schedule reflect the latest development progress?
should reflect. However, the method should be used to administer the Baseline Schedule: maintaining a stable Schedule, and then nourish an updated alterations. Baseline approximate should be used for other Spec.
12. your work is for the estimate of every human own it?
everyone should own estimates. Workload estimates from bottom-up rather than down from the previous distribution. Unless there are other reasons, such as the political task of fixed period and so on.
13. you start from the project developers to work overtime?
not the circumstance. Do not start to agree in combat fatigue. From the start of the project to work overtime and can only show progress of the project is unreasonable. Of course, some of the software outsourcing to work overtime each day, it belongs to the scope of exploitation.
14. your project maneuver in the Buffer Time is added to the back of each small task it?
not. Buffer Time added to the back of each small task, it is effortless to be consumed accessible. Buffer Time increases to the whole or a checkpoint in front of a Milestone.
15. worthy to spend more time, from 95% to attain 100% nice
worth it, well worth it. In particular, the time when the project afterward became exhausted, should adhere to. This will bring about a qualitative difference between products.
16. registration of new defects, if stating the steps to reproduce?
to. This is the communication between the Dev and Test tools. Face to face communication needs, fill out a Repro Steps need.
17. to write new code to resolve known defects before going to it?
to. Each person's deficiencies tin not exceed 10 or 15,GHD Purple Gift Set, or the age bug have to be determined in array to persist to write new code.
18. your priorities for defects prior agreement with it?
must be defined. Severity to points 1,2,3, admitted well: blue and Data Lost calculate Sev 1, Function Error calculate Sev 2, the operator interface Sev 3. However, this convention can be adjusted appropriately Quality of product.
19. you have differ views of the defects of the three meetings it?
must have. Have a clear decision-making process. This is alike to the CCB (Change Control Board) concept.
20. All the defects were closed by the end of the person enrolled it?
Bug should be closed by the Opener. Dev can not be privately closed Bug.
21. you hate the programmer to adjust the old code it?
aversion is customary. Solution is to organize Code Review, a time to be left solo. XP is also a means.
22. your project group Team Morale Activity it?
out once every month, eating, singing, Outing, play, karting, etc., must be. Do not left the money.
23. your team have its own Logo it?
to have your own Logo. Should at least have their own Codename.
24. your employees with corporation Logo for T-Shirt it?
have. Can enhance the sense of belonging. Of course, T-Shirt do see good, it is best to do with the 80 cotton. Do not wear a few times to ragged.
25. General Manager by fewest every month to enter the second project group meeting
want. Concern that high-level team member to make this project.
26. You are to open a branch for each Dev it?
opposition. Branch Merge workload management and too error disposed.
27. It was a long Check-In Code does not it?
no. For most projects,GHD Diamond Flag 2011, up to 2 alternatively three days you ought Check-In.
28. In Check-In code to fill out when they annotate that?
to write at least one or two sentences, such as If you sprint uphill pull, which also counted as
29. have not set a day deadline Check-In?
want to explicit Check-In Deadline. Otherwise, Build Break.
30. you can compile always the source code once the installation files?
ambition. This is a everyday compilation (Daily Build) basis. And must be skillful to make automatic.
31. your team to do a daily build it?
surely do. There are three entities that software project / product evolution necessary: ​​1. Bug management; 2. Source control; 3. Daily build.
32. your company have amassed a list of project risks?
to. Risk Inventory. Otherwise, the afterward project started, and the only racking our brains Risk Analysis.
33.
devise for easy as feasible for simple as possible. Designed to put extra words in the hereafter may send endless trouble. Should be brave from the starting cut. Called coverage treatment.
34. to make full use of existing products, technology, code
do not own everything Coding. BizTalk and Sharepoint is the best example of these two as a basis for raising the threshold digit. Or you can use as numerous as possible of the existing Control classes. Or try to use XML, preferably than trying to work to Parse a txt file; try to use RegExp, preferably than their own operation from scratch string, and so on and so ahead. This is the
to. Preferably about once a month. Early final annual, rumors Stevb Windows group stopped a month below the bid of improved security. Btw,
36. your team everyone wrote Daily Report it?
write. Five minutes is ample to write about 10 words, differentiate their own group of people what I've done today. One for communication, two spur themselves (if laze day, ambition be embarrassed to write their own).
37. Your project manager will issue a Weekly Report it?
to. But also for communication. Including the present progress, the possible risk, quality status, the progress of manifold jobs and so on.
38. your whole team is at least encounter once a week?
to. Must be met. Programmers hate meetings, but the meeting period each week increase up to at least 4 hours. Including the team meeting, spec reiterate meeting, bug triage meeting. Do not we focusing instead on writing code.
39. your project team to discuss all record it?
pre-sent meeting apply and program,GHD Leopard Grain, will the people responsible for conducting and recording, behind the people responsible for issuing meeting minutes, which are efficacious meeting points. Also, each session should be fashioned agreements and action items.
40. additional divisions know your team doing it? Newsflash
to mail some great organizations as a whole. Show your team's merit. Otherwise, when you sit inside the lift, and other departments were asked: