• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Open / Drupal Camp Presentation: Brent Bice
 

Open / Drupal Camp Presentation: Brent Bice

on

  • 808 views

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 ...

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.

Statistics

Views

Total Views
808
Views on SlideShare
808
Embed Views
0

Actions

Likes
0
Downloads
9
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Name, title, years worked at LevelTen and subject of presentation
  • We use a process called Scrum which allows us to work from a prioritized Product Backlog (list of requirements) Every 2-4 weeks (Sprint) we review the Product Backlog, the team determines what they can work on for the next 2 weeks based project priority and add it to the Sprint Backlog.
  • Why is strategy and planning important
  • Through interviews, surveys, online research and asset collection we document business goals…etc. The outcome is…
  • Testing notes.
  • Testing notes.
  • Testing notes.
  • Testing notes.
  • Testing notes.
  • Testing notes.
  • Why is strategy and planning important
  • Why is strategy and planning important

Open / Drupal Camp Presentation: Brent Bice Open / Drupal Camp Presentation: Brent Bice Presentation Transcript

  • [MM.DD..YY] [PRESENTER] Planning and Executing a Successful Drupal Implementation 2010 PLANNING AND IMPLEMENTING A SUCCESSFUL DRUPAL WEBSITE Brent Bice [email_address] Twitter: #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 Automated Marketing Systems Content Delivery Networks Digital Asset Management Online Media Kits 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
    • Delivery Failure
      • Time, Budget and/or Scope
      • Technical Debt
    • Requirements Failure
      • Client
      • User
    • Strategic Failure
      • Did not align with business goals
      • Did not generate ROI
      • 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 manage our projects
  • From Waterfall to Agile Project Lifecycle 2 week cycles
  • Scrum 24 hours 2-4 weeks
  • Strategy and Planning
  • 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 Brief
    • Creative Brief
    • Technical Brief
    • Competitive Features Matrix
    • Marketing Analysis
    • Wireframes
    • Product Backlog
      • User Roles
      • User Stories
  • User 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
  • User Role Modeling potential customer 5 job seeker content editor
  • User Stories 5 As a content editor, I can add, edit and remove content.
  • User Stories 5 As a job seeker, I can search for available positions close to where I live.
  • User Stories 5 As a potential customer, I can view a list of services on the website and learn more about them.
  • User Stories create the product backlog 24 hours 2-4 weeks User Stories Prioritized by importance (MSCW)
  • Site engineering meetings to create tasks
    • Content types
    • Site recipes
    • Module selection
    • Risk assessment
    • Impediments
    • Test cases
  • Tasks 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 the product 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 Meeting Stories | Tasks | Impeded | In Progress | To Verify | Done
  • Daily Scrum Meeting
    • Every morning the team meets at the board
    • Every 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 long
    • Members are responsible for themselves
  • User Stories create the product 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.
  • Creative Creative Briefs to Concepts
    • Creative Brief
    • Wireframes
    • Mood 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 Boards
    • Represent 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
  • Comps
    • Static 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
  • Brent Bice [email_address] Twitter.com/brentbice Thank You!
  • Experience Counts
  • Content Management Framework Standards Compliant Accessible Modular Stable Customizable Open-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 …”