Embed Size (px)
DESCRIPTION
In this session we'll discuss how agile analysis and project management processes can be applied to Drupal implementation. We'll discuss the setting of expectations for stakeholders when planning and executing a Drupal project, and how to avoid the typical pitfalls. You'll also learn how a multi-disciplined project team can smooth your project execution, and increase your chance for overall success.
Citation preview
[MM.DD..YY] [PRESENTER]
Planning and Executing a Successful Drupal Implementation
2010 PLANNING AND IMPLEMENTING A SUCCESSFUL DRUPAL WEBSITE
Brent [email protected]: #ocdplanning
Changes since 2000:Change in websites from being simple one
way information resources to more functional and application driven websites.
The involvement of the user in the creation process.
Web services allowing the use and distribution of content and other information.
Increasing the economic value of the Web as an integral part of commerce.
Complex site structures
SEO
Video
Email PPC
Directed Content
CRM
AutomatedMarketing Systems
Content DeliveryNetworks
Digital AssetManagement
Online MediaKits
Media Room
Blog
Wiki
Forum
PDFs
Workflow
Multiple Languages
User Permissions
2009 Project Success was Rare
Average cost overrun: 45%Time overrun: 63%Functionality delivered on average: 67%
32%
44%
24%
Chaos Report by The Standish Group: Application Delivery
Modes of Failure
1. Delivery Failure1. Time, Budget and/or Scope2. Technical Debt
2. Requirements Failure1. Client2. User
3. Strategic Failure1. Did not align with business goals2. Did not generate ROI3. Did not align with other marketing initiatives
Why do projects fail?
We are asked to estimate something that’s intangible.
Communication problems during requirements gathering – client/user vs. development team.
Business models/requirements change often which changes the scope of work.
How do we reduce risk?
Estimating – DO NOT FIX-BID!!! Give ranges for time and cost and work on retainer.
Communication – adequate planning and frequent conversations. Win the battles and you’ll win the war.
Execution – show work as quickly as possible and iterate. 80/20
Change – evaluate models/goals often and make changes based on data at hand.
How we manageour projects
From Waterfall to Agile
Project Lifecycle
2 week cycles
Scrum
24 hours
2-4 weeks
Strategy and Planning
Goals of strategy:Goals of strategy:
5
To learn as much as we can about our client’s business objectives, customers’ needs, and competitive position.
Document findings and make recommendations.
Create a strategy that aligns business goals, satisfies customer needs, and strategically positions the client for success.
Photo by: inklake
Outcomes of Research:
Goals and Objectives
Brand BriefCreative BriefTechnical BriefCompetitive
Features MatrixMarketing AnalysisWireframesProduct Backlog
User RolesUser Stories
User Role Modeling and StoriesUser Role Modeling and Stories
5
Open lines of communication between team members
Gain better understanding of the system being designed
Identify who will be using the system
Understand how they will be using the system
Create user stories for the product backlog
potential
customer
User Role ModelingUser Role Modeling
5
jobseeker
contenteditor
User StoriesUser Stories
5
As a content editor, I can add, edit and remove content.
User StoriesUser Stories
5
As a job seeker, I can search for available positions close to where I live.
User StoriesUser Stories
5
As a potential customer, I can view a list of services on the website and learn more about them.
User Stories create theproduct backlog
24 hours
2-4 weeks
User StoriesPrioritized by importance (MSCW)
Site engineering meetingsto create tasks
Content typesSite recipesModule selectionRisk assessmentImpedimentsTest cases
Tasks to complete storyTasks to complete story
5
As a potential customer, I can view a list of services on the website and learn more about them.
Create “services” content type with title, body, image upload.Create a list view of services that displays title, teaser, image, and link to product page.
Configure user permissions to allow unauthenticated users to view services content.
We assign points to Stories
We assign hours to Tasks
User Stories create theproduct backlog
24 hours
2-4 weeks
User Stories and associated Tasks are estimated by the entire team and added to the Sprint Backlog
Development and Testing
Site Building and Verification
Production environment setup: SVN
Development
Int. testing
Content
Client testing
Daily Scrum MeetingStories | Tasks | Impeded | In Progress | To Verify | Done
Daily Scrum Meeting
Every morning the team meets at the boardEvery team member must answer 3 questions
What did you do yesterday?What are you going to do today?Are there any impediments?
Meetings are between 15-20 minutes longMembers are responsible for themselves
User Stories create theproduct backlog
24 hours
2-4 weeks
Goal of sprint is to provide client with a potentially releasable feature.We review feature with client, gather feedback and make decision based on that feedback.
CreativeCreative Briefs to Concepts
Creative BriefWireframesMood Boards
Comps
Wireframes A website wireframe is a
basic design draft done before any artwork and used in web design to show the structure of a website, custom user paths, most important user interface elements, their position and relationships between website pages.
Axure helps us rapidly prototype layouts for usability testing, etc.
Mood BoardsRepresent a mood, atmosphere or feeling as a way to research ideas for future comps that will be created.
Sets creative expectations
Gives designers better direction for comps
Saves time an money
CompsStatic look and feel of the final website.
Sets creative direction
Considerations
Always gather feedback from Drupal developers before sending to client
Pixel perfect comps
How we succeed:Estimating – DO NOT FIX-BID!!! Give ranges
for time and cost and work on retainer.
Communication – adequate planning and frequent conversations.
Execution – show work as quickly as possible and iterate. 80/20
Change – evaluate models/goals often and make changes based on data at hand.
Continuously improve
Experience Counts
Content Management Framework
Standards Compliant
AccessibleModular
Stable
CustomizableOpen-Source
Facts:Tens of thousands of developers are involved in developing, testing, debugging and maintaining the framework and modules.
Drupal falls under GPL licensing meaning that everyone/anyone can use code and contribute freely.
There are over 4,000 contributed modules.
Tektronix developers are already learning Drupal.
Who’s Using Drupal For Knowledge Management
What Businesses Are Saying
Rackspace
"The new site was designed to give our customers immediate access to the support documentation they need. We took our existing support information, re-wrote it, organized it into categories and subcategories, and built a new search system so you can find your answers in a hurry ..."
“We considered using Clearspace to be our CMS of choice but by early 2008 the absence of certain features and other issues made us consider other options. We had a front-end developer working on adding more blogs to blogs.zappos.com and a new hire, Geoff, who we assigned to about.zappos.com. The idea was to let each work on their projects and occasionally switch places and work on the other CMS so they could compare and contrast the features and development time. Drupal ended up being superior in terms of templating and development as well as adding new features and ease of use for the end user.”
Zappos
Associated Press - Obama Administration Source
“The White House has ditched the proprietary content management system that had been in place since the days of the Bush Administration in favor of the latest version of the open-source Drupal software…”
