Planning

This marks the start of the project. In this phase:

• Present the project objectives
• Give a name to the product that we’ll be developing
• Set the ground rules
• Identify the Product Owner
• Set the time table
  • Development
  • Collection
• Agree on the site structure (Information Architecture)
• Have the design approved (Information Design)
• Breaks down the product into Components
• Develop prototypes

Component Releases

For each component, we go through the entire software development cycle.

• Component Analysis
  • Product Owner and Spinweb discusses the requirements (Analysis)
• Component Design
  • Spinweb produces the Product Specifications (Design)
  • Product Owner approves the Product Specifications (Design) [Signoff]
• Component Development
  • Spinweb starts coding (Development). The development team holds daily 15-minute meetings to ensure the project on track and on time.
• Component Testing
  • Spinweb conducts internal testing and debugging (Testing)
  • Spinweb releases Component for testing (Testing)
  • Product Owner tests the Component (Testing)
  • Spinweb immediately addresses the issues (Testing)
• Product Owner accepts the Component – Component Acceptance. [Signoff]

Product Release

This marks the end of the project. Product Owner accepts the product (for formality) – Product Acceptance. [Signoff]

Support

Spinweb allocates an appropriate amount of time for bugs and errors.