【文章內(nèi)容簡(jiǎn)介】
has met its goals. Whatever criteria you choose should be realistic, measurable, documented, and aligned with what quality means to your customers.Tip 4: Negotiate mitments. Despite pressure to promise the impossible, never make a mitment you know you can’t keep. Engage in goodfaith negotiations with customers and managers about what is realistically achievable. Any data you have from previous projects will help you make persuasive arguments, although there is no real defense against unreasonable people.Planning the WorkTip 5: Write a plan. Some people believe the time spent writing a plan could be better spent writing code, but I don’t agree. The hard part isn’t writing the plan. The hard part is actually doing the planning—thinking, negotiating, balancing, talking, asking, and listening. The time you spend analyzing what it will take to solve the problem will reduce the number of surprises you have to cope with later in the project.Tip 6: Depose tasks to inchpebble granularity. Inchpebbles are miniature milestones. Breaking large tasks into multiple small tasks helps you estimate them more accurately, reveals work activities you might not have thought of otherwise, and permits more accurate, finegrained status tracking.Tip 7: Develop planning worksheets for mon large tasks. If your team frequently undertakes certain mon tasks, such as implementing a new object class, develop activity checklists and planning worksheets for these tasks. Each checklist should include all of the steps the large task might need. These checklists and worksheets will help each team member identify and estimate the effort associated with each instance of the large task he or she must tackle.Tip 8: Plan to do rework after a quality control activity. Almost all quality control activities, such as testing and technical reviews, find defects or other improvement opportunities. Your project schedule or work breakdown structure should include rework as a discrete task after every quality control activity. If you don’t actually have to do any rework, great。 you’re ahead of schedule on that task. But don’t count on it.Tip 9: Plan time for process improvement. Your team members are already swamped with their current project assignments, but if you want the group to rise to a higher plane of software engineering capability, you’ll have to invest some time in process improvement. Set aside some time from your project schedule, becau