Skip to main content

Best Practices for Software Projects: Design Signoffs

Article

Best Practices for Software Projects: Design Signoffs

Member Submitted Article by Steve Miller | Comments: (0) | Wed, 06/23/2004 - 13:55
Summary:

Ever worked on a project where the requirements were scribbled on a napkin and you were asked how quickly you could get the project done? First time project managers sometimes fall into this trap, and it is a recipe for disaster.

To consistently deliver software solutions on-time and on-budget, you must follow a disciplined approach to managing the project. The only way to adequately determine the project timeline is to fully understand all deliverables of a project, to manage risk with risk mitigation, and to obtain signoffs along the way so that you have documented accountability.

Here is a simplified overview of how a software project should be run to ensure on-time and on-budget delivery. Notice that each phase requires sign-off from various project members to ensure a quality release.

Files: 
application/pdf iconBest Practices for Software Projects: Design Signoffs
No votes yet
About The Author: Steve Miller
View More

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.

More like this

Site Contents
Back To Top