DEVELOPMENT SERVER
Rules to Better Work Items ( AKA Project Management )

Figure: Remember, a batter aims to hit the ball way out of the ballpark. Don't set an indefensible boundary too early

• An architectural roadmap recommending technical solutions
• Time allocated for further specification work to be included in each Release. At SSW we only create detailed specifications for 3 releases at a time
• A breakdown of the required software application into its core components, likely to include the approximate number of main features (e.g. screens, reports or sitemap)
• An integration plan
• A deployment strategy
• A 'future functionality' wish list - requiring the client to set the priorities for the project through defining what is in and out of scope
• A detailed list of 'issues' associated with the existing system which impact future development and maintenance
• Hardware and licensed software recommendations
• A sample mock-up screen where the project is less than one month

Sample Initial Release Plan

1. Release 1 (1.5 man months) - Database schema design
2. Release 2 (1.5 man months) - Development Module 1 Customers
3. Release 3 (1.5 man months) - Development Module 2 Products
4. Release 4 (1.5 man months) - Development Module 3 Orders
5. Release 5 (1.5 man months) - Development Module 4 Suppliers
6. Release 6 (1.5 man months) - Development Modules 5 Employees

With the Initial Release Plan, the client can see whether SSW understands their business and the requirements for their software development project. The ballpark estimate allows them to decide whether the project is feasible for their budget and time-frame.