1.
Do you have a source code management tool using the source code management tool? Should be used. VSS, CVS, PVCS, ClearCase, CCC / Harvest, Firefly can. My choice is VSS. 2.
Do you have a defect management system using the defect management system? Should be used. ClearQuest is too complicated, my recommendation is bugzilla. 3.
Do your test groups still write test cases with Word? Don't use Word write test cases (Test
Case
). You should use a specialized system, you can be Test
Manager
It can also be a small website that develops ASP.NET. The main purpose is TRACK and BROWSE. 4.
Have you built a portal? Have a portal, used to put Contact
Info
Baselined
Schedule
, News, etc. Recommended SharePoint
Portal
Server
2003
To achieve, 15 minutes will be done. Can't buy SPS
2003
WSS
(Windows
SharePoint
Service)
. 5.
Your project group uses you to buy the best tool? It should be used to work with as much as possible. For example, you should write C # with vs.net instead of notepad. Most of the NOTEPAD write programs is just a kind of show. But also take into account funds, so say "you can buy the best." 6.
Do your programmers work in a quiet environment? Need a quiet environment. This is extremely important, and it is necessary to ensure that each person's space is greater than a certain area. 7.
Does your employees have a phone call? Need a phone call. Moreover, the phone is preferably with message function. Of course, such a set of message telephone system overhead is not small. However, at least one phone call must have, don't do anyone standing up and shout: "a phone call". "People" is strongly condemned this approach. 8.
Everyone knows who everyone knows? should know. Any feature should at least have an Owner. Of course, Owner can continue dispatch to others. 9.
Have you encountered someone say "I thought ..."? To eliminate "I thought". NEVER
Assume
Anything
. 10.
Are all people in your project group sitting together? need. I oppose Virtual
Team
Also opposed DEV in the United States, Test in China. It is best to sit together, and it will be more beneficial. 11.
Does your schedule reflect the latest development progress?
Should be reflected. However, you should use the Baseline method to manage schedule: maintain a stable Schedule, and then maintain a latest change. The method of Baseline should also be used for other SPECs. Baseline is an important means in the management of the change management. 12.
Is your workload to be estimated by everyone? Everyone should be estimated. To estimate the workload from the bottom, not from top to bottom. Unless other reasons, such as the policy of the political task. 13.
Do your developers work overtime from the beginning of the project? do not do that. Don't make a fatigue war at the beginning. Overtime work from the beginning of the project, only the project progress is unreasonable. Of course, some of the day software outsourcing must work overtime every day, and that belongs to exploitation. 14.
Buffer in your project plan
Time
Is it added behind each small task? Don't. Buffer
Time
Add it after each small task, it is easy to easily consume. Buffer
Time
Together, add it in front of a MILESTONE or CheckPoint. 15.
It is worth more to spend some time, from 95% to 100%, it is worth it. Especially when the project is buddy, it is necessary to persist. This will bring quality difference to the product. 16.
When you register new defects, do you write a reproduction step? want. This belongs to the communication between DEV and TEST. Facing your face communication, fill in Reprosteps in detail
also need. 17.
Do you solve known defects before writing a new code? want. Every person's defect cannot exceed 10 or 15, otherwise you must first solve the old BUG to continue writing new code. 18.
Do you have a prior agreement on the defects? Must be defined. Severity points 1, 2, 3, agreement: Blue Screen and Data
Lost
SEV
1
, Function
Error
SEV
2
, Calculate SEV on the interface
3
. But this agreed can be adjusted appropriately according to the product quality status. 19.
Do you have a three-country meeting to the shortcomings of opinions? Must have. There is a clear decision process. This is similar to CCB
(Change)
CONTROL
Board)
the concept of. 20.
All defects are all closed by the registered person? BUG should be shut down by Opener. DEV cannot close Bug privately. twenty one.
Do your programmers disgusted to modify the old code? Avoiding is normal. Solution is to organize CODE
REVIEW
Allow time. XP is also a way. twenty two.
Your project group has Team
Morale
Activity
? Every month must work once, eat, sing, outing, play, open kart, etc., must have. Don't leave these money. twenty three.
Does your project group have their own logo? Be your own logo. At least there should be its own CODENAME. twenty four.
Does your employees have T-shirt with company LOGO? There is. Enhance the sense of belonging. Of course, T-Shirt is better to do, preferably use 80 cotton. Don't wear a few times and break down. 25.
The general manager participates at least a monthly meeting meeting at least monthly. Let Team
MEMBER
I feel that the high level pays attention to this project. 26.
Do you open a branch for each dev? Oppose. Branch management and Merge workload is too large, and it is easy to make mistakes. 27.
Does anyone don't check-in code for a long time? No. For most items, you should check-in for up to two or three days. 28.
Fill in the comment when check-in code? To write, at least one or two sentences, such as "solve the bug
NO
.25
"
. If you pull high, this is also part of the "Configuration Audit". 29.
Is there a final deadline for CHECK-IN every day? To be, clear CHECK-IN
Deadline
. Otherwise it will be build
Break
. 30.
Can you compile all the source code into an installation file?
need. This is a daily compilation (Daily
Build
)Foundation. And you must be able to make automatic. 31.
Do your project groups make daily compile? Of course you have to do. There are three things that are necessary for software projects / product development: 1.
Bug
MANAGEMENT;
2.
Source
CONTROL;
3.
Daily
build
. 32.
Does your company have accumulated a list of projects? want. Risk
Inventory
. Otherwise, when the next project starts, it can only take a head to analyze Risk. 33.
The more simple design is, the better, the better. There is more words when designing, it will bring endless troubles in the future. Shop should be chopped from the beginning. This is called Scope
Management
. 34.
Try to use existing products, technology, and code, don't do something yourself. BizTalk and SharePoint are the best examples. There are two as the foundation that can increase the starting point. Or you can try as much as possible. Or try to use XML instead of yourself to Parse a text file; try to use regexp instead of your own operation string, and so on. This is the embodiment of "software reuse". 35. Are you stopped to consolidate the code over a period of time? want. It is best to one month. Learn last year, the Windows group stopped in STEVB's command to enhance security. BTW, "" This word "hang", first voice. 36.
Everyone in your project group writes daily
Report
? To write. Five minutes is enough, write about 10 sentences, telling yourself what I have done today. One for communication, two spur yourself (if you are free day, you will be embarrassed). 37.
Your project manager will issue weekly
Report
? want. Also communicated. The content includes current progress, possible risk, quality status, progress in various work. 38.
Do you meet at least every week of your project group? want. Be sure to meet. The programmer hates the meeting, but at least 4 hours each week is at least 4 hours. TEAM
Meeting,
SPEC
REVIEW
Meeting,
Bug
Triage
Meeting
. Don't worry about it. 39.
Do you have a record in your project group? Meeting forward
REQUEST
And Agenda, some people are responsible for hosted and record, and some people will be responsible for Meeting.
minutes
This is EFFECTIVE
Meeting
Key points. Moreover, every meeting must form agreements and action
Items
. 40.
Does other departments know what your project group is doing? Send some newsflash to the entire major organization. Show
Your
Team
'S
Value
. Otherwise, when you sit in the elevator, the people in other sectors ask: "What are you doing?" When you answer the "ABC Project", others don't know, the feeling is not very good. 41.
The benefits of all formal communication Email via Email are reluctant. However, it is also necessary to avoid overkill, the best way is to say first, and when email is confirmed. 42.
Establish multiple mailing for the project group
Group
If you are in Ad Exchange, you will build a distribution.
List
. For example, I will build ABC
PROJECT
Core
Team
, ABC
PROJECT
DEV
Team
, ABC
PROJECT
All
Tester
, ABC
PROJECT
Extended
Team
and many more. This is convenient to initiate email, and people who can receive email are received, and should not be harassed. 43.
Everyone knows where to find all the documents? Everyone should know. This is called knowledge management (Knowledge
Management
). The most convenient thing is to put the document in a concentrated file.
Share
The better way is to use SharePoint. 44.
Do you make a decision, tell everyone the reason? To tell everyone the reason. Empower
Team
MEMBER
One of the means is to provide sufficient information, which is one of several principles of MSF. Indeed, Tell
ME
why
Human temperament, tell
ME
why
We can have understanding. Chinese people do things like to engage in restrictions, restrict information, and those who can see a document are people with identity. Big wrong. Authority, power, is not that it can be access
Information / Data
And is that it is to master resources. 45.
STAY
Agile
and
EXPECT
change
To be this. The demand will change, and the code that has been written will be modified. Do your psychological preparation, don't resist Change, but Expect
change
. 46.
Do you have a full-time software tester? There is a full-time test. If the person is not enough, you can peer
Test
Exchange the test. Don't test your own yourself. 47.
Your test has a general plan to specify what to do and how to do it? This is Test
Plan
. Do you want to do performance testing? Do you want to do a USABILITY test? When do you start testing performance? What is the standard passing? What is the means, automatic or manual? These issues need TEST
Plan
To answer. 48.
You should write Test first
Case
Then test it again? It should be. It should be designed and programmed first, first TEST
Case
Test again. Of course, things are flexible. I sometimes make up Test while doing the first pass.
Case
. As for Test first
Case
Developed again, I don't like it, because I am not used to it, it's too trouble, as for others, try it. 49.
Will you create a test case for a variety of input portfolios? Don't, don't engage in border conditions. When the heart combination explosion. There are a lot of Test
Case
Tools can automatically generate a combination of various boundary conditions - but want to clear, do you have time to run so much Test?
Case
. 50.
Can your programmers see test cases? want. Let DEV see TEST
Case
Bar. We are all come together for the same purpose: improve quality. 51.
Do you have some people to do ease of use?
To do this. I look at my own program interface, how to see it is pleasing. This is called aesthetic fatigue - it is not smelling for a long time. It is used to it. 52.
Are you the expectation of automatic testing? Don't expect too much. According to me, in addition to performance test, I still forget "automatic test", forget WinRunner and LoadRunner. For the status quo of domestic software test, it can only be "correctly" must pass. " 53.
Does your performance test do etc. All functions are done? can not be like this. Performance tests cannot be returned to a so-called "system test" phase. Early measurement, early death, early death. 54.
Do you notice the insecticide effect in the test? Bug has anti-drug resistance, BUG is also. The new bug found is less and less normal. At this time, it is best to exchange the Tested Area, or use other tools and techniques, will find some new bugs. 55.
Can someone in your project group say the current overall quality of the product? There is. When the boss asks this product, what is the current quality, Test
Lead / Manager
Should be responsible for answering. 56.
Do you have a unit test? Unit tests must be. However, there is no unit test, I have done a project that has no unit test, and it will be successful - it may be lucky, maybe everyone is the relationship of the family. Still, software engineering is very practical, very engineered, very flexible, some methods will be better than others in some cases, and vice versa. 57.
Your programmer throws the wall after writing the code? Badge. After writing a program, even if you don't do unit test, you should run a run. Although there are special testers, people who do developing are not doing it. Microsoft also has Testrelease
Document
The saying, the program is too bad, the test has the right to kick it. 58.
Do all functions in your program have input checks? Don't. Although it is said to do an input check is Write
Secure
code
Key points, but don't do too much input check, the parameter passes between some internal functions do not have to check, save yourself. The same reason, not necessarily written to all functions. It is enough to write some main. 59.
Does the product have a unified error handling mechanism and an error interface? There is. It is best to have unified error
Message
, Then each error
Message
Brought an Error
Number
. In this way, users can according to ERROR
Number
User
manual
Look at the specific description and possible reasons for the mistake, just like SQL
Server
The mistake is like. Similarly, ASP.NET also has a unified Exception process. Can refer to the related Application
Block
. 60.
Do you have a unified code writing norms? There is. Code
Convention
Many, you can send it to everyone. Of course, if there is a FXCOP tool to check the code is better. 61.
Everyone knows the business meaning of the project? want. This is Vision meaning. Don't take the project only as a job. Sometimes I want to be a pioneer in the informationization of a certain industry in China, or tell Team from time to time.
MEMBER
This project can save money for a certain national department, which has a certain amount of taxpayer's money, which has power. Ordinary things can also have a noble goal. 62.
Does the interface and operation habits of each part of the product? To be this. To make users feel that the entire program seems to be written by one person. 63.
There is a Cool as a highlight of the promotion
FEATURE
? want. This is an enhanced team cohesiveness, confidence. Moreover, "a junior huns", there is a highlight to cover some problems. In this way, for the customer, it feels that the product is still an acceptable from a quality point of view. Or, Cool
FEATURE
Or the highlight can make up for the measures after a quality problem. 64.
Short the startup time of the product as much as possible. Software start time (start-up
Time
) The customer's first impression of performance. 65.
Don't pay too much attention to the external impression programmer in the first eye, it is easy to make this error: Too much weight, stability, storage efficiency, but ignore the external feelings. And the high-level manager, the customer is opposite. These two aspects should be taken into account and coordinate these is the work of PM. 66.
Do you have developed according to the detailed product function manual? To be this. It is necessary to have a design to develop. Design documentation, you should say how this product will run, and you should take some stories. Don't diamond details when design, don't drill into the database, code, etc., those behind them, those behind, and step in step. 67.
Do everyone review the functional design before began to develop and test? To do it. FUNCTION
SPEC
REVIEW
It is used to unify thinking. Moreover, REVIEW has formed a consensus later, no one can say anyone in the future, "You see, I am against such a designed, now I have a bitter." 68.
Everyone always thinks the THE
Whole
Image
? To be this. Although everyone is only manufacturing a leaf, everyone should know how they are in the tree in which they are manufactured. I oppose the software blue collar, opposed excessive development of software manufacturing to the pipeline, workshop. See section 61. 69.dev
Is the division of work is simple or horizontal? It cannot be simply divided according to the functional module, or in a single score according to the performance layer, the intermediate layer, the database. I recommend this: First, according to the function module, then each "layer" has an Owner to review owner's design and code to ensure consistency.
70.
Your programmer write a programming document? want. However, I heard that Microsoft's programmers did not write before 1999. So, it is not absolute writing, and it is sometimes possible. See Article 56. 71.
Do you write a program when you recruit it? need. I like to make a string and list of questions. This topic has a lot of loops, judgments, pointers, recursive, etc. 72.
Do you have a technical exchange? need. Every two worships have internal TECH
Talk
Or Chalk
Talk
Bar. Let the team members share the technical experience, this spent is sent to the outside to train. 73.
Can your programmers focus on one thing? Let the programmer focus on one thing. For example, a department has two projects and 10 people. One way is to let 10 people participate in two projects, each of each item spends 50% time; another method is 5 people going to project A, 5 Personal to project B, each person is 100% on a project. I must choose later. There are many people in this truth understand, but many leaders practices themselves as a resource that can be split. 74.
Your programmer will exaggerate the time required to complete a job? Yes, this is common, especially in the later stage of the project, the time required to do a change, boycotting Change in a time. The method of solving is to sit down and slowly, grind the programmer's counter-opposite, together analyze, and make the granular particles of the estimated time be smaller. 75.
Try not to use Virtual
HEADS
It is best not to use Virtual
HEADS
. Virtual
HEADS
Means resource
IS
NOT
Secure
Shared
Resource
It will reduce the work efficiency of Resource, which is easy to increase the chance of error, and people who will use the two people don't have much time to go to REVIEW.
SPEC
, REVIEW
DESIGN
. A Dedicated person, it is necessary to have two people who can only put 50% time and energy. I have lost your loss: 7 parts
Time
Tester, discovered bugs and dry live, add up, not as if two full-time. See Section 73. 73 are for programmers, 75 are targeted for Resource
Manager
of.
