Upload
achieve-internet
View
487
Download
0
Tags:
Embed Size (px)
DESCRIPTION
While often overlooked or just considered a necessary obligation, project documentation can play a crucial in a project's success. Documentation should be much more than the training manual that no one has time to create before a site launches, it should serve site of collaboration and play an important role at every stage of a project’s lifecycle. This slideshow will reflect on the role of documentation and describe a process-oriented approach to performing project discoveries.
Citation preview
Communicating Drupal: Documentation and Discovery
Jeff Traynor
7/15/14
Prepared For: DrupalCamp LA 2014
Solutions Architect
Achieve’s Footprint
What would you say you do here?
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.
Achieve at a GlanceLongevity
Scale
Physics
Environment
Cost of Construction
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
!
Feasibility Study
Business Requirements
Why?
Business Requirements
Customer ProfileStrategic Initiative Problem Analysis
Goals & Objectives Target Audience
Stakeholders Project Team
Timeline & Milestones
Business Requirements
Who?
User Personas
Schematic Design
Information Architecture
Where?
Information Architecture
!Documents Produced:
• Sitemap Diagrams• User Flow Diagrams• Systems Integration Diagrams
Design Development
Prototyping
What?
Prototyping
Construction Documents
Functional Requirements
How?
Functional Requirements
Functional Requirements
Features Content Types
Taxonomies Views
Modules Workflows
Integrations
Functional Requirements
Proprietary Specifications vs
Performance Specifications
Contract Administration
Architecture & Planning
!Documents Produced:
• Epics & User Stories• DevOps Plan• Development Plan• Sprint Plan and Milestones
•
Thank You
it’s not magic, it’s excellence.
Jeff Traynor Solutions Architect
[email protected] @jtray