Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scoping Digital Projects as a Non-Developer (10.10.17)

133 views

Published on

An overview of one possible way to scope digital projects.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Scoping Digital Projects as a Non-Developer (10.10.17)

  1. 1. Scoping Digitalprojects asanon-developer Jay Hoppie CEO, Alpha Particle http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  2. 2. The importance of projectscoping • Informs and protects all stakeholders • Allows you to accurately charge for your work • Is essential for prioritizing features http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  3. 3. Whatwewill be covering initialclientcommunication examples of informationarchitecture decomposition of projectcomponents what to dowhen something goesawry& other Tips http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  4. 4. apotentialclientapproaches youwithaproject http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  5. 5. Projectoverview • An industry-specific publisher wants a new website to replace their existing site • The client already has designs • The client does not have a thorough RFP http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  6. 6. Projectoverview
  7. 7. DISCOVER IS aService http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  8. 8. Initialclientcommunication • Discuss goals of project — all decisions made by any stakeholders should support the project goals. • Make it clear that that the client should not assume any functionality will be present in the final project that was not discussed beforehand. • Establish any major project limitations, such as cost, launch date, or stakeholder review process. • Agree on necessary IA documents • Document all decisions http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  9. 9. ATALL TIMES COMMUNICATE CLEARLYANDWITH CONFIDENCE http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  10. 10. INFORMATIONARCHITECTURE • User Flows • Site Map • Content Matrix • Wireframes • Feature Descriptions • User Stories http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  11. 11. Decomposition into componentparts Scoping and prioritizing individual components of a project. By breaking a project into smaller parts, we can more accurately gauge the time needed to complete a component and the risk associated with that component. http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  12. 12. Decomposition into componentparts • Granularity is important, both in terms of component size and unit of estimation • Ideally components will be of a size that all stakeholders can easily grasp as a discrete and important portion of the project. Examples include page templates, navigation, and third-party integrations • Small, discrete features can be grouped in feature sets • Each component can be estimated individually, both in terms of build time needed and risk http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  13. 13. Things to considerwhen scoping • Front-end functionality vs controlling logic • Patterns & connectivity • Static vs dynamic content • Third-party integrations http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  14. 14. Other things to consider • Supported environments (browsers, devices, screen sizes) • Quality Assurance & staging environments • Deployment & Hosting • Data migration
 http://alphaparticle.com AlphaParticle • Content development & entry • Stock imagery & other design components • User setup & training • Stakeholder review • Ad providers Jay@alphaparticle.com
  15. 15. Abrief demonstration http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  16. 16. Presentation of Scope • Share the scope and supporting documentation with the client. • Discuss prioritization & dependency • Avoid structuring projects as fixed bid http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  17. 17. Whathappenswhen things gowrong • If a component takes longer to build than estimated, the most important thing to do is establish the cause of the difference. Stakeholders are much more accepting of changes in scope or cost if they understand what happened. • In addition to the cause, share your plan to address this issue. This may include a change order, revised timeline, or a revised scope. • Maintaining your position as an expert is important. • Avoid frequent scope changes. http://alphaparticle.com AlphaParticle Jay@alphaparticle.com
  18. 18. Other tips • Honesty is the best policy • Estimate your estimation time • You are not ‘figuring it out’ - you are researching • Avoid the terms ‘easy’ or ‘hard’, use language that describes resources • Avoid structuring projects as fixed bid • Be willing to refund or reallocate fees if completed early http://alphaparticle.com AlphaParticle • Aggressively identify any ambiguity or red flags • Deny all attempts at scope creep, but document if it does occur • Require a design review • Large contracts are great, but can inhibit accurate estimation • Always account for a Phase II Jay@alphaparticle.com
  19. 19. Questions? http://alphaparticle.com AlphaParticle https://twitter.com/jay_hoppie jay@alphaparticle.com Jay@alphaparticle.com

×