7 Steps for Successful Project Management
Upcoming SlideShare
Loading in...5
×
 

7 Steps for Successful Project Management

on

  • 3,036 views

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

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

Statistics

Views

Total Views
3,036
Views on SlideShare
3,036
Embed Views
0

Actions

Likes
0
Downloads
17
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

7 Steps for Successful Project Management 7 Steps for Successful Project Management Presentation Transcript

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