Amsterdam Pm Web Process


Published on

  • Be the first to comment

  • Be the first to like this

Amsterdam Pm Web Process

  1. 1.
  2. 2. discovery<br />Take the time to understand what you’re really after. Lots of examples, lots of discussion about what you need vs. what you want, talks about how you’ll use the site, what you hope to gain, how visitors will navigate your new site. <br />specification<br />Put things down on paper, make sure they make sense. Identify everything that needs to be considered, consider it, plan it. All future actions stem from the specification, testing will be performed against the spec.<br />design<br />The fun part. Bringing color to all the things discussed in the previous two phases. Functionality comes into better focus, how the site will be used becomes for apparent, your brand is finally applied.<br />development<br />The boring part. The heads-down, quiet-music-playing-in-the-background phase of the project. Opportunity to get stuff done on your end, to get the building blocks built and to make course corrections as needed.<br />build & test<br />Putting things together and seeing if they work. Really, it’s like that. Sometimes adding content will break the design, sometimes a solution to a business problem is inadvertently discovered, we always use an issues list to track what needs to be done. <br />go live<br />The big day, and everything that goes into it: SEO plan, advertising plan, hosting situation, DNS transfer, training, email blast to existing clients… the launch party. Most importantly, the launch party.<br />
  3. 3.
  4. 4. discovery<br />Talk about abstracts.<br />Lay down some thoughts on paper and build on them.<br />Put up the scaffolding. Generate increasingly more complete wireframes until the scope is clear and the specification process can start.<br />What’s a Wireframe?<br />
  5. 5. You say:<br />“We’re an Interior Design company, so, we have tons of pictures that we want to highlight on the home page. Our market is very segmented, so we want to be able to speak to each segment on the home page before directing them to their own dedicated pages.” <br />
  6. 6. You say:<br />“Yes, but our images are smaller than that. And we need to have the ability to place images in the text section as well. In fact, we would like to make that section a blog that we update daily or weekly. And our CEO wants a new tagline with the logo.” <br />
  7. 7. You say:<br />“And we need to have visitors sign up for our mailing list.” <br />“Got it. Let’s talk about your market segments.” <br />I say:<br />
  8. 8.
  9. 9.
  10. 10. specification<br />Describe each element of each page.<br />Record all integrations with 3rd party applications, databases, payment systems, etc. <br />Spell out how visitors will use your site.<br />Spell out how you will use the site.<br />What’s a Spec look like?<br />
  11. 11. It looks like this…<br />Describe each element of each page.<br />Record all integrations with 3rd party applications, databases, payment systems, etc. <br />Spell out how visitors will use your site.<br />Spell out how you will use the site.<br />
  12. 12. And like this…<br />Outlines everything the designers and developers need to know to build the site.<br />
  13. 13.
  14. 14.
  15. 15. design<br />Options presented based on wireframes and specification.<br />Chance to discuss the visual as well as continue the visitor experience discussion.<br />Set of page templates delivered<br />What’s a design comp?<br />
  16. 16. wireframe<br />Designs are based on the information and functional descriptions provided in the specification, as well the layout presented in the wireframes. <br />design example 1<br />Literal interpretation of wireframe.<br />Main elements presented as outlined in the spec.<br />Main image rotates to display market-segment-specific images, though market navigation is not clearly defined in this example.<br />
  17. 17. design example 2<br />Less literal interpretation of wireframes. <br />Market segmentation is presented inside the main image, with navigation moving to a horizontal access, but overall similar in layout to the presented wireframes. <br />
  18. 18. design example 3<br />Least literal interpretation. <br />Market segments are divided by the panels, which flip upon roll-over to present a new, market-specific image and link to landing page. More modern design, uses Flash.<br />
  19. 19.
  20. 20.
  21. 21. development<br />Is boring.<br />Is an opportunity for you to get things wrapped up on your end, like content creation.<br />Consists of heads-down work, rarely attractive.<br />How do we stay coordinated?<br />
  22. 22. basecamp<br />Online project management tool.<br />Access to your project provided at start of project.<br />Tracks all milestones, files, comments, To-Do’s, etc. in real time. <br />Eliminates confusion about project direction, scope. <br />Continuous record of communications and decisions made.<br />
  23. 23.
  24. 24.
  25. 25. build and test<br />Fit all the pieces together.<br />Generate all pages of your site, begin filling with your content.<br />Testing performed by us relative to spec, by you according to your vision.<br />How do we track issues?<br />
  26. 26. basecamp<br />Issues, bugs, defects, things that just aren’t right go in Issues List.<br />Each issue has an owner.<br />Real-time collaboration, does not replace good ol’ phone conversations.<br />Goal is to resolve all issues.<br />
  27. 27.
  28. 28.
  29. 29. go live<br />Site is built, testing is complete, all issues resolved.<br />Flip the switch… <br />Click to see Site Live!<br />