7 Steps for Successful Project Management


Published on

This presentation looks at executing the 7 steps needed to take an account from a prospect to a finished product.

Published in: Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

7 Steps for Successful Project Management

  1. 1. 7 Steps for Success <ul><li>Project Management that works </li></ul>
  2. 2. #1 The Prospect <ul><li>First Meeting with a new Client, Lead, or Prospect </li></ul><ul><li>Gather all client provided materials </li></ul><ul><li>Survey Prospect with list of questions in the following: </li></ul><ul><ul><li>Content </li></ul></ul><ul><ul><li>Design </li></ul></ul><ul><ul><li>Development </li></ul></ul><ul><ul><li>SEO/UX </li></ul></ul><ul><li>Get as much information and specifications as possible! </li></ul>
  3. 3. #2 Team Evaluation <ul><li>Have each team leader evaluate the project for their particular specialty. </li></ul><ul><ul><li>Content / UX </li></ul></ul><ul><ul><li>Design </li></ul></ul><ul><ul><li>Development </li></ul></ul><ul><ul><li>SEO / on going UX </li></ul></ul><ul><li>Have Team create “Features List” and estimates broken down to hours. </li></ul><ul><li>Package all “Feature Lists” into ONE called the “Backlog” ...we can change the name for this. </li></ul>
  4. 4. #2 Team Evaluation The Backlog Content Design Development SEO 8 3 6 12 8 12 6 8 12 6 8 12 6 12 Copy 12 hours homepage 2 about page 2 team bios 2 services page 2 products page 2 contact page 2
  5. 5. #3 The Proposal <ul><li>From the “Backlog” we should have an accurate proposal for the client. </li></ul><ul><li>Provide the entire “Backlog” to the client to approve that we covered all project features along with price. </li></ul><ul><li>IF client makes changes to the feature list repeat #1 and #2. </li></ul><ul><li>IF the client approves “Backlog” - CONGRATS!!! </li></ul>
  6. 6. #4 Release Plan <ul><li>Refresh “Backlog” and create Product Release Plan and Schedule. </li></ul><ul><li>Create Milestones (Sprints) based on the provided “backlog”, team availability, and client timeline. </li></ul><ul><li>Create each milestone to have a working deliverable. </li></ul><ul><ul><li>This varies with the need of client and desire of team. </li></ul></ul><ul><li>Create each milestone to be between ONE week and FOUR weeks depending on priority and scope. </li></ul><ul><li>Create at least FOUR milestones if possible. </li></ul>
  7. 7. #4 Release Plan The Backlog Content Design Development SEO Milestone 1 Milestone 2 Milestone 3 Milestone 4
  8. 8. #5 The Sprint Cycle <ul><li>Begin development with the first Milestone </li></ul><ul><li>Follow the full development cycle for each milestone ending with a workable tested product. </li></ul><ul><ul><li>Spec Milestone </li></ul></ul><ul><ul><li>Build </li></ul></ul><ul><ul><li>Test and Q.A. </li></ul></ul><ul><ul><li>Get Approved </li></ul></ul><ul><ul><li>Repeat! </li></ul></ul>
  9. 9. #6 Final Q.A. <ul><li>After completion of each milestone Q.A. the entire integration of each milestone and approve the production product. </li></ul><ul><li>Final Q.A. is a sprint so don’t forget the “backlog” </li></ul><ul><ul><li>“ Backlog” is SO important to track and stay on task </li></ul></ul><ul><li>IF scope changes and client finds MORE to do request the product to go BETA and begin on going UX. </li></ul><ul><ul><li>IF client declines beta start back at step #1 </li></ul></ul><ul><li>Prepare for NEXT RELEASE by taking everything the client wanted that didn’t make it through development and create a “Post Release Backlog” </li></ul>
  10. 10. #7 Launch <ul><li>Launching to site should be SIMPLE! </li></ul><ul><li>All development should NOT be domain dependent. </li></ul><ul><ul><li>If domain dependents exist create a sprint backlog and begin sprint process. </li></ul></ul><ul><li>Things to consider BEFORE LAUNCH: </li></ul><ul><ul><li>Hosting </li></ul></ul><ul><ul><li>Redirects </li></ul></ul><ul><ul><li>Domain Dependents ( SSL, 3rd Party API keys, etc. ) </li></ul></ul><ul><ul><li>Emails </li></ul></ul>
  11. 11. Conclusion Notes <ul><ul><li>Agile Development Pet Peeves </li></ul></ul><ul><ul><ul><li>Do Not Be A Hero, get REAL! </li></ul></ul></ul><ul><ul><ul><ul><li>its ok to make a mistake just make it EARLY and communicate with everyone! esp. client. </li></ul></ul></ul></ul><ul><ul><ul><li>Detail Guessing and Concept Design </li></ul></ul></ul><ul><ul><ul><li>LONG Sprints </li></ul></ul></ul><ul><ul><ul><li>Communication </li></ul></ul></ul><ul><ul><ul><li>Micro-management </li></ul></ul></ul><ul><ul><ul><li>Slow to reality </li></ul></ul></ul><ul><ul><ul><ul><li>“ A Website is a Living Organism” </li></ul></ul></ul></ul><ul><ul><ul><ul><li>GIVE BIRTH TO AN INFANT NOT AN ADULT. </li></ul></ul></ul></ul>