How apt cultivate the quality of the project team

How to cultivate the quality of the project team? (Rpm)
1. your team to use source code management tool that?
should be used. VSS, CVS, PVCS, ClearCase,GHD Deluxe Midnight 2011, CCC / Harvest, FireFly tin. My alternative is VSS.
2. your project team using the defect management system that?
should be used. ClearQuest too perplexing, 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 amplify an ASP.NET their own small websites. The cardinal intention is to Track and Browse.
4. Your team has not built a portal?
to have a portal to let Contact Info, Baselined Schedule, News and more. Recommended Sharepoint Portal Server 2003 to achieve 15 minutes to obtain. Can not afford to buy 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 used VS.NET instead of Notepad to write C #. Procedures are normally equitable use Notepad to write a show off. But it should also take into list the asset, so that is
6. your programmers work in a quiet environment it?
absence a quiet context. This is extremely important, merely also to assure that everyone over a definite zone of ​​space.
7. your staff that everyone has a call it?
need a phone per human. And tel with voicemail feature is best. Of course, aboard such a phone system with message on the head of is not small. But at least 1 phone per human 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 one should have a Owner, of course, Owner can continue to Dispatch to others.
9. Have you ever had somebody mention,
to exclude, Never suppose everything.
10. your team all the people all sitting nigh it?
needs. I disapprove the Virtual Team, also opposed Dev in the United States, Test Development in China this way. Could sit attach sit together on the best, the benefits of a very, very much.
11. Does your schedule reflect the latest development progress?
should reflect. However, the method ought be secondhand to administer the Baseline Schedule: maintaining a stable Schedule,GHD Purple Gift Set, and then nourish one updated alterations. Baseline reach should be used for other Spec.
12. your work is for the estimate of each person own it?
everyone should own estimates. Workload estimates from bottom-up rather than down from the previous delivery. Unless there are other reasons, such as the political task of nailed period and so on.
13. you start from the project developers to work overtime?
not the circumstance. Do not start to engage in battle 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 intend in the Buffer Time is added to the back of each small task it?
no. Buffer Time joined to the behind of every small task, it is effortless to be consumed lightly. Buffer Time increases to the entire alternatively a checkpoint in front of a Milestone.
15. worthy to spend extra time, from 95% to achieve 100% nice
worth it, well worth it. In particular, the time when the project later became exhausted, should adhere to. This will bring about a qualitative feud between products.
16. registration of new defects, whether stating the treads to reproduce?
to. This is the communication among 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 ahead going to it?
to. Each person's deficiencies can not exceed 10 or 15, or the old bug must be determined in mandate to proceed to jot fashionable code.
18. your priorities for failings prior concert with it?
must be defined. Severity to points 1,2,3, coincided well: blue and Data Lost count Sev 1, Function Error calculate Sev 2,GHD IV Black Straighteners, the operator interface Sev 3. However,GHD Blue Straighteners, this convention can be accommodated appropriately Quality of product.
19. you have alter views of the defects of the three meetings it?
must have. Have a clear decision-making process. This is similar to the CCB (Change Control Board) conception.
20. All the defects were closed by the end of the person registered it?
Bug should be closed along the Opener. Dev can not be privately closed Bug.
21. you hate the programmer to adjust the old code it?
aversion is regular. Solution is to mobilize Code Review, a period to be left solo. XP is too a means.
22. your project group Team Morale Activity it?
out once monthly, eating, singing, Outing,GHD IV Mini Straighteners, activity, karting, etc., have to 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 workers with company 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 least every month to enter the second project team meeting
ambition. Concern that high-level crew membership to make this project.
26. You are to open a branch for each Dev it?
against. Branch Merge workload management and too error disposed.
27. It was a long Check-In Code does not it?
not. For maximum projects, up to two or three days you should Check-In.
28. In Check-In code to fill out when they comment that?
to write at least one or two sentences, such as If you scamper uphill pull, which also counted as
29. have not set a day deadline Check-In?
want to remove Check-In Deadline. Otherwise, Build Break.
30. you can compile all the source code once the installation files?
want. This is a daily compilation (Daily Build) basis. And must be proficient to make auto.
31. your team to do a daily build it?
certainly do. There are 3 things that software project / product evolution necessary: ​​1. Bug management; 2. Source control; 3. Daily construct.
32. your enterprise have amassed a list of project risks?
to. Risk Inventory. Otherwise, the afterward project began,GHD IV Styling Set, and the merely racking our heads Risk Analysis.
33.
chart as easy as possible as easy as possible. Designed to put more words in the future may bring endless difficulty. Should be brave from the starting mow. Called range management.
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, rather than trying to go to Parse a txt file; try to use RegExp, rather than their own action from scratch string, and so on and so forth. This is the
to. Preferably about once a month. Early final annual, rumors Stevb Windows group stopped a month below the mandate of promoted security. Btw,
36. your team everyone wrote Daily Report it?
write. Five minutes is ample to write approximately 10 words, narrate their own group of people what I've done today. One for communication, two spur themselves (whether sleepy daytime, will be entangled to write their own).
37. Your project director ambition publish a Weekly Report it?
to. But also for communication. Including the present progress, the likely risk, quality status, the progress of various jobs and so on.
38. your whole team is at least encounter once a week?
to. Must be met. Programmers dislike meetings, but the meeting time each week add up to at least 4 hours. Including the team meeting, spec reiterate meeting, bug triage meeting. Do not we focusing instead on book code.
39. your project team to argue always record it?
pre-sent meeting request and programme, will the folk responsible for conducting and recording, behind the people responsible for issuing meeting minutes, which are effective meeting points. Also, each conference should be fashioned agreements and operation items.
40. other departments understand your team doing it? Newsflash
to bring some large organizations as a whole. Show your team's amount. Otherwise, when you sit inside the hoist, and other departments were asked: