| |
|
|
Creating a Project Template for Estimations of Time, Tasks, and Resources
By Nannette Thacker - 09/02/1999
- Plan Phase
- Estimations of Work for Development
- Include time for all applicable tasks shown below
- Multiply result by 1.5 to allow for interruptions and unexpected issues
- Meetings
- Project/Timeline planning meeting
- Review of Functional Requirements Specifications
- Development Team Meeting to Assign Tasks
- Weekly status review meetings with analyst or business unit
- Weekly status review meetings with development team
- Review printed project schedule
- Update percents completed
- Add new tasks not accounted for
- Modify dates on existing tasks as necessary
- Analyze Phase
- Research and read all existing documentation on project
- Ask any needed questions in advance as possible
- Review existing source code as needed
- Design Phase
- Documentation
- Project work plan for development
- Alter the template to create a project work plan for development
- Update the project work plan bi-weekly
- Weekly print updated project work plan
- Weekly distribute printed work plans to team members and lead
- Detailed Design Specification (DDS)
- DDS extends throughout duration of entire project
- Update DDS throughout project as logic and code changes are made
- DDS Outline for Project Lead
- Create detailed design specification from template
- Create an overview paragraph
- Include developers and analysts assigned to project
- Include work flow as applicable
- Include files, directories altered or created
- Include session/application objects created
- Include database tables altered or created
- Include risks and assumptions applicable to development
- Refer reader to Functional Requirements Specification for overall project risks and assumptions as needed
- Build Phase
- System Admin Duties
- Set up development/test environment
- Create project branch in code control
- Assign code control rights to project developers
- Coding
- Coding alterations or additions
- Break each item in Functional Requirements Specification into tasks
- Comment all source code with date, initials, project name, description of change
- Don't delete old code, comment out. Can be deleted at a later date - months later.
- Primary developer tests changes as they are made
- Test Phase
- Unit Testing
- Primary developer writes test plans (step-by-step instructions) for each change or enhancement
- Beta tester is assigned Overall Unit Testing utilizing test plans
- Beta tester documents any needed changes after testing
- Test results are sent back to primary developer
- Primary developer makes any needed code changes
- Unit testing steps are looped through until all pass
- Code Review
- For new development or major changes to pages
- Typically takes 2 hours of preparation by Moderator
- Developer prints out source code pages to be reviewed
- Developer gives master printout to Moderator
- Moderator prepares list of evaluators (2-3)
- Moderator makes copies of pages and distributes to evaluators
- Moderator provides evaluation templates to evaluators
- Evaluators spend approximately 1-2 hours in advance reviewing code
- Moderator arranges meeting
- Meeting takes 3-4 hours
- Developer explains project and overview
- Evaluators walk through code, looking for code or logic errors
- Errors are identified and documented
- Solutions are NOT discussed at the meeting
- Moderator keeps people on track
- Developer does not moderate or evaluate
- This is NOT to critique the developers style or lack thereof
- If there is another way to do it, but the way done works, move on!
- At end of 3rd hour, meeting dismissed
- 4th hour is used for those who want to stay and discuss solutions
- Moderator compiles list of needed changes, distributes to developer
- Developer is responsible for incorporating changes as needed
- Dog and Pony Show
- For enhancements and features to existing code
- Call together group of 2 or more individuals
- Walk through the work flow from a user perspective
- Demonstrate how product works and changes made
- Bugs always pop up when you're showing off to someone
- System Testing
- QA Support throughout system testing
- Alterations of code throughout system testing
- Unit testing as needed for new changes
- Update to documents as needed
- Check out and check in of code as needed
|
|
