Scope deter­mi­na­tion, the first mile­stone, is also one the major goals of a soft­ware design. A project scope deter­mines where all of the project’s resources should focus their atten­tion. It has a tremen­dous effect on our project com­mu­ni­ca­tion, our pri­or­i­ti­za­tion, our test strat­egy, our devel­op­ing effort and so on. Attain­ing a the func­tional demands writ­ten down in a scope usu­ally means suc­cess for a soft­ware project so it’s an impor­tant aspect indeed. Let’s see what phases needs to be con­cluded in order to have a scope.

• Soft­ware Project Phase 1.1: Draft­ing the Project Plan
• Soft­ware Project Phase 1.2: Draft­ing the Soft­ware Design
• Soft­ware Project Phase 1.3: Dis­cussing the Soft­ware Design
• Soft­ware Project Phase 1.4: Allo­cat­ing Time­lines, Deter­min­ing Final Deadline
• Soft­ware Project Phase 1.5: Reach­ing Agreement

Related posts:

1. Soft­ware Project Trait #5: Scope
2. Soft­ware Project Trait #7: Project Iterations
3. Soft­ware Project Trait #1: Hall Stand
4. Soft­ware Project Trait #4: Milestones
5. Soft­ware Project Trait #6: Meetings