Communicating Drupal: Documentation and Discovery
1 like1,192 views
The document discusses the importance of documentation in the context of architecture and project management as presented by Jeff Traynor at DrupalCamp LA 2014. It emphasizes three principles of great architecture: durability, functionality, and beauty, and highlights how effective documentation can enhance clarity, accountability, and collaboration throughout the project lifecycle. Key components mentioned include feasibility studies, functional requirements, and various documentation types such as sitemaps and user stories.
Communicating Drupal: Documentation and Discovery
- 1. Communicating Drupal: Documentation and Discovery Jeff Traynor Solutions Architect Prepared For: DrupalCamp LA 2014 7/15/14
- 2. Achieve’s Footprint What would you say you do here?
- 3. Architecture In De Architectura, Marcus Vitruvius Pollio describes three fundamental principles which great architecture should accomplish: • Firmatis: It should stand up robustly and remain in good condition — it should be durable. • Utilitas: It should be useful and function well for the people using it — it should be functional. • Venustatis: It should delight people and raise their spirits — it should be beautiful.
- 4. Achieve at a Glance Longevity
- 5. Scale
- 6. Physics
- 7. Environment
- 9. Documentation Matters Documentation is a source of clarity • “If you can’t explain it to a six year old, you don’t understand it yourself” – Albert Einstein Documentation is a mechanism for accountability • Managing budgets, scope, an expectations • Advocating for project stakeholders Documentation is a site of collaboration • Documenting process and collaborative creation • Recording the decision making process !
- 12. Business Requirements Customer Profile Strategic Initiative Problem Analysis Goals & Objectives Target Audience Stakeholders Project Team Timeline & Milestones
- 14. User Personas
- 15. Schematic Design
- 17. Information Architecture ! Documents Produced: • Sitemap Diagrams • User Flow Diagrams • Systems Integration Diagrams
- 20. Prototyping
- 24. Functional Requirements Features Content Types Taxonomies Views Modules Workflows Integrations
- 25. Functional Requirements Proprietary Specifications vs Performance Specifications
- 27. Architecture & Planning ! Documents Produced: • Epics & User Stories • DevOps Plan • Development Plan • Sprint Plan and Milestones •
- 28. it’s not magic, it’s excellence. Thank You Jeff Traynor Solutions Architect jeff.traynor@achieveinternet.com @jtray