Your SlideShare is downloading. ×
ReliefWeb | DevSeed Meeting | 03 Sep 2010
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

ReliefWeb | DevSeed Meeting | 03 Sep 2010

479
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
479
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ReliefWeb & Development Seed: Building Status, Design, and Planning Thursday, September 2nd
  • 2. Agenda • Concepting & Strategy Update (Eric G.) • Build Progress Update (Eric G.) • Drupal 7 Update (Eric G.) • Lunch • Design Review (Eric G.) • Build Plans (Alex B.) • Taxonomy/Content Update (Mark M.) • Project Management Overview (Ian C.) • Planning for Launch & Support (Eric G.) • Q&A (All)
  • 3. Development Seed’s Summer Focus: • Concepting + strategy • Technical architecture • Design • Prepping for Drupal 7
  • 4. Development Seed’s Summer Focus: • Concepting + strategy focusing on making it: • Easier to add content to the site • Easier to find content + jobs on the site • Easier to see all types of content the site offers • Balancing expanding audience w/ building for power users
  • 5. Development Seed’s Summer Focus: • Technical Architecture • Going Drupal 6 vs. Drupal 7 • Key modules needed • Importing content • Integration with the jobs site • Making everything wicked FAST!
  • 6. Development Seed’s Summer Focus: • Design Goals • Focus on the content • Light = FAST! • Clean
  • 7. What is done: • Concepting and strategy • Technical architecture ~70% (need to present plan in official writeup still) • Designs ~ underway • Key module refactoring • Drupal 7 technical base prep
  • 8. What is NOT done: • Drupal 7
  • 9. Drupal 7 • It is late.
  • 10. Yes.... that really says October 27th
  • 11. ... and we think that date is optimistic
  • 12. What does a Drupal 7 slow down mean? • Drupal 7 is _still_ the right choice. • We are actively building on Drupal 7 for you, in its pre release state. • This is messing with our timing badly • ... and costing us a lot more.
  • 13. Drupal 7 • Under development for 3 years • Primary base for the next 2 years AKA you will have access to the latest new tools by being on the latest platform • Reducing total costs of ownership by reducing an upgrade cycle. • More attractive for developers to work on.
  • 14. Timing and cost plans: • Development Seed is burdening almost all of the Drupal 7 costs on this project. • This is long term strategic investment for the larger international development space. • We are adjusting our build plans to try to stay on target. (Alex will speak to this) • We need to slip delivery till December 3rd,
  • 15. Design: this is not another website
  • 16. Design process: going agile
  • 17. Agile Design • There are still mockups. • mockups ensure: • style/theme • general layout • information architecture • The designs need to be flexible though.
  • 18. How to make design flexible • Go with the grain of the software • Reducing total costs of ownership via upgrades. • Taking advantage of built in workflows. • Experimenting and playing. • Things will need to change
  • 19. Design: this is not another website
  • 20. My ReliefWeb
  • 21. Keeping it simple to help users know where to go
  • 22. River of fresh updates
  • 23. Where events are happening
  • 24. Hilight key emergencies
  • 25. Hilight other key content on ReliefWeb
  • 26. format for LOTS of updates
  • 27. Visualization tools
  • 28. filter in context in-context power filtering
  • 29. Real time mapping of reports
  • 30. Show key emergencies + make it easy to find countries
  • 31. Better integration of jobs
  • 32. add context to countries
  • 33. feature key reports
  • 34. trying to better integrate emergencies w/ countries
  • 35. integration with data.worldbank.org
  • 36. river of updates
  • 37. which can be visualized
  • 38. and filtered by everything!
  • 39. Building reliefweb.int
  • 40. How do you normally build a web site?
  • 41. Plan Build Migrate Review Adjust Launch
  • 42. You’ll be waiting for us
  • 43. Light build + early migration to move up reviews + launch
  • 44. Plan Build Migrate Review Adjust Launch
  • 45. Plan Light build Build Migrate Review Adjust Launch
  • 46. Plan Light build Migrate | Build Review Adjust Launch
  • 47. Plan Light build Migrate | Build Review Adjust Launch
  • 48. Step I DS builds light shell site (won’t need all of Drupal 7) Delivery: 3rd week of September
  • 49. Step 2 RW migrates content (DS helps) Delivery: End of October
  • 50. Step 3 DS builds out site (parallel to migration) Delivery: First week of November
  • 51. Step 4 RW reviews Delivery: mid November
  • 52. Step 5 DS delivers adjustments Delivery: First week of December
  • 53. Step 6 Final QA and launch Expected launch date: mid December
  • 54. Plan Light build Migrate | Build Review Adjust Launch
  • 55. The Process
  • 56. Agile = Working Code, Fast
  • 57. Why Agile? ✓ Prioritize Launch Date ✓ Ensure Top Quality on What Is Delivered ✓ Collaborate to Manage Scope & Risk
  • 58. Result: Very Tight Site Delivered ASAP
  • 59. Fixed Elements • Content Migration (including Jobs) • Core Site Functionality • New Design • Drupal 7 • Stable Launch in December • THEN Additional Phase 1 Scope
  • 60. Gathering Feedback
  • 61. Feedback Process • All Ideas Welcomed & Captured Online • Overall Backlog Triaged with Mark McCarthy • Priority Ideas Moved to Phase 1 Backlog • Remaining Ideas Saved for Phase 2
  • 62. What is Phase 2?
  • 63. Phase 2 • New Aggregation Solution • Community Features • ReliefWeb “Apps” • TBD?
  • 64. Result: Very Tight Site Delivered ASAP
  • 65. ReliefWeb’s Involvement
  • 66. ReliefWeb Tasks September: • Confirm Design (early Sept.) • Confirm Migration Plans (early Sept.) • Confirm Hosting Plans (mid Sept.) • Confirm Overall Architecture (late Sept.) Outcome: Solid Plan by End of September
  • 67. ReliefWeb Tasks October: • Do Basic Migration into Drupal (early Oct.) Outcome: Content in Drupal by end of October
  • 68. ReliefWeb Tasks November: • Review Content in New Site (mid Nov.) • Training on Using New Site (mid Nov.) Outcome: Migration Done by end of November
  • 69. ReliefWeb Tasks December: • QA Final Site (early Dec.) • Launch Site (mid Dec.) Outcome: New ReliefWeb Live in December
  • 70. Risks • Launching Before Christmas • Support Plans