October 24th, 2008 chris
The following are a list of items that should be reviewed in software development projects:
- Marketing documents, requirements specifications, use cases, and analysis models
- Business process models and business rules
- Project charter documetns and all kinds of project plans (project management plan, task list, schedule, configuration management plan, quality assurance plan, risk management plan, and so on)
- Architecture descriptions
- User interface designs and prototypes
- Software and databse design descriptions and models
- Source code, including scripts, macros, stored procedures, and the like
- Program documentation and system maintenance documentation
- Test plans, designs, cases, and procedures
- User guides, reference manuals, help screens, tutorials, training materials, and field and customer support manuals
- Build, release, and installation procedures
- Software development procedures, standards, and process descriptions
Posted in Reviews
October 24th, 2008 chris
In every endeavor that we undertake to improve the quality of our process in the software development life cycle we need to have the support and commitment of management. Majority of the people in management doesn’t always understand what software reviews are and the importance of it to shipping quality products on time. The following are the signs that your management is committed to software reviews:
- Providing the resources and time to develop, implement, and sustain an effective review process
- Setting policies, expectations, and goals about review practice
- Maintaining the practice of reviews even when projects are under time presure
- Ensuring that project schedules include time for reviews
- Making training available to the participants and attending the training themselves
- Never using review results to evaluate performance of individuals
- Holding people accountable for participating in reviews and for contributing constructively to them
- Publicly rewarding the early adopters of reviews to reinforce desired behaviors
- Running interference with other managers and customers who challenge the need for reviews
- Respecting the review team’s appraisal of a document’s quality
- Asking for status reports on how the program is working, what it costs, and the team’s benefits from reviews
Posted in Reviews