Sharpen your axe drupal concph 2010
•
0 recomendaciones•825 vistas
Presentation by Richard jones @ DrupalCon Copenhagen
Recomendados
Recomendados
Más contenido relacionado
Destacado
Similar a Sharpen your axe drupal concph 2010
Similar a Sharpen your axe drupal concph 2010 (20)
Último
Último (20)
Sharpen your axe drupal concph 2010
- 1. Sharpen your Axe- How We Reduced Development Time by more than 80% Richard Jones 25. aug 17:15 VPS.net Wednesday, 25 August 2010
- 2. Some Context • Richard Jones • Technical Director of i-KOS, UK Digital Agency • Working with CMS since 1999 • @richardjones Wednesday, 25 August 2010
- 3. My CMS Journey • 2000-2001 Cable & Wireless NCompass Resolution (now Microsoft CMS) • 2002 - 2007 i-KOS SiteSolved, proprietary J2EE • 2008 - Enlightenment Wednesday, 25 August 2010
- 4. Our Early Experiences • Welcome to Drupal 6 • The Learning Curve • 1 requirement, 1000 possible solutions • The Drupal Way (and why some Drupal Contractors are better than others) Wednesday, 25 August 2010
- 5. Our Early Drupal Sites • Took longer to implement • Were difficult to maintain • Used different techniques and modules • Were confusing for Site Owners • Were generally disappointing Wednesday, 25 August 2010
- 6. How We Used to Do Things • Design / PSDs • Web Kit • Build Structure • Content • Testing • Training / Support Wednesday, 25 August 2010
- 7. What Really Happened • Design / PSDs • Web Kit • Build Structure • Rework Webkit to make it work in CMS • Rework Design to work around limitations of CMS • Multiple Loops of Above Wednesday, 25 August 2010
- 8. Time for a Reboot Wednesday, 25 August 2010
- 9. The Opportunity to Change Everything • Not limited to the technology • Design and User Experience • Process of Selling • Development • Training / End User Experience Wednesday, 25 August 2010
- 10. Consider Every Role • Designer (Visual and UX) • Developer • Themer • Site Owner • Site End User • Trainer • Business Development • Sys Admin Wednesday, 25 August 2010
- 11. Common Causes of Project Slippage Scope Creep Unclear Requirements Impractical Design Communication Content Wednesday, 25 August 2010
- 12. “The System” • Complexity • Estimated Saving • Learning Curve • Resistance • Overall Benefit Wednesday, 25 August 2010
- 13. Design to a Grid Design to a Grid (960) • Multidivisional - 12 / 16 / 24 • Consistency • Speed of Production Complexity Medium • Doesn’t have to limit Estimated Saving Learning Curve High Short design scope Resistance Medium Overall Benefit High Wednesday, 25 August 2010
- 14. Develop a Toolkit Develop a Toolkit • Admit the Truth • Focus on most common requirements • Get them right without pressure Complexity High Estimated Saving Huge! • Dedicated R&D even Learning Curve Resistance Short Low better Overall Benefit High Wednesday, 25 August 2010
- 15. Selling Out of the Box • Sales control the project Sell out of the Box scope • Now you have a toolkit, sell it! • Features you don’t have will always cost more than a client wants to pay Complexity Low Estimated Saving High • Even if “there’s a module for Learning Curve Short that” Resistance High Overall Benefit High • Easier to price jobs Wednesday, 25 August 2010
- 16. Reverse the Workflow Reverse the Workflow • Design LAST! • Design to the prototype • Prepare the client Complexity Estimated Saving Learning Curve Low Medium Medium Resistance Extreme Overall Benefit High Wednesday, 25 August 2010
- 17. Evolutionary Prototype Evolutionary Prototype • Parallel Running • Allows customer to add content before design • Work out kinks in user experience before Complexity Medium theming Estimated Saving Learning Curve Medium Medium Resistance Medium • Test functionality Overall Benefit High Wednesday, 25 August 2010
- 18. The StartPoint The StartPoint • Start with a great site from install • Turn off features you don’t need • Stop repeating Complexity Estimated Saving Medium High yourself Learning Curve Resistance Medium Medium Overall Benefit High Wednesday, 25 August 2010
- 19. Focus on the Site Owner Site Owner Experience • Build from the beginning with the site owner in mind • Consider how site can be maintained • Make Drupal invisible Complexity Estimated Saving High Medium • Learning Curve High Real Users don’t care Resistance Low about the technology Overall Benefit High Wednesday, 25 August 2010
- 20. Select Your Team Pick the Team • Different Skills Required • Less Technical • More Business Savvy Complexity Estimated Saving Learning Curve High Medium Medium Resistance Medium Overall Benefit High Wednesday, 25 August 2010
- 21. Putting it Together Design to a Grid (960) Reverse the Workflow Site Owner Experience Pick the Team Develop a Toolkit Evolutionary Prototype Sell out of the Box The StartPoint Complexity Medium Complexity Low Estimated Saving 30% Estimated Saving 25% Complexity High Learning Curve Complexity Short High Learning Curve Medium Complexity High Resistance Estimated Saving Medium Medium Complexity Saving Resistance Estimated Medium Extreme Medium Estimated Saving 50% Learning Curve Medium Overall Benefit Learning Curve High High Estimated Saving Overall Benefit High 30-40% Learning Curve Short Resistance Medium Resistance Low Learning Curve Medium Complexity Low Resistance Low Complexity Overall Benefit HighMedium Overall Benefit High Resistance Medium Estimated Saving 40% Overall Benefit High OverallEstimated Saving Benefit High 30-40% Learning Curve Short Learning Curve Medium Resistance High Resistance Medium Overall Benefit High Overall Benefit High Wednesday, 25 August 2010
- 22. Live Demo Wednesday, 25 August 2010
- 23. So where does the 80% come in? Wednesday, 25 August 2010