Principles that guide process
1. Be agile
2. Focus on quality at every step
3. Be ready to adapt
4. Build an effective team
5. Establish mechanisms for communication and coordination
6. Manage change
7. Assess risk
8. Create work products that provide value for others
Principles that guide practice
1. Divide and conquer
2. Understand the use of abstraction
3. Strive for consistency
4. Focus on the transfer of information
5. Build software that exhibits effective modularity
6. Look for patterns
7. When possible, represent the problem and its solution from a number of different perspectives
8. Remember that someone will maintain the software
Communication principles
1. Listen
2. Prepare before you communicate
3. Someone should facilitate the activity
4. Face-to-face communication is best
5. Take notes and document decisions
6. Strive for collaboration
7. Stay focused; modularize your discussion
8. If something is unclear, draw a picture
9. (a) Once you agree to something, move on. (b) If you can’t agree to something, move on. (c) If a feature or function is unclear and cannot be clarified at the moment, move on.
10. Negotiation is not a contest or a game. It works best when both parties win.
Planning principle
1. Understand the scope of the project
2. Involve stakeholders in the planning activity
3. Recognize that planning is iterative
4. Estimate based on what you know
5. Consider risk as you define the plan
6. Be realistic
7. Adjust granularity as you define the plan
8. Define how you intend to ensure quality
9. Describe how you intend to accommodate change
10. Track the plan frequently and make adjustments as required
Modeling principle
1. The primary goal of the software team is to build software, not create models
2. Travel light don’t create more models than you need
3. Strive to produce the simplest model that will describe the problem or the software
4. Build models in a way that makes them amenable to change...