Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Successes and Challenges When Managing Large Scale Drupal Projects

Large scale Drupal projects are a special breed of Drupal project typically found with large enterprise customers. They involve managing multiple initiatives, partners, stakeholders and product owners. When development is performed by round-the-clock, globally distributed teams, project management complexity compounds. It’s critical that everyone understands the part they need to play. When executing projects with this scale, it can become challenging to maintain efficient agile workflows.

To give your next large scale project team a head start, we've identified processes and methodology improvements that can be easily implemented to make your Drupal project successful. In this webinar, we’ll discuss how an effective Drupal project manager can keep everyone on task, on track, and prepared for worst case scenarios.

Specifically, we’ll:

-Review key elements of communication that uphold the agile process
-Discuss elements of good team management: from delivery and infrastructure support to product owner and stakeholder
-Talk through key tools and practices to keep your project humming

Related Books

Free with a 30 day trial from Scribd

See all
  • Login to see the comments

  • Be the first to like this

Successes and Challenges When Managing Large Scale Drupal Projects

  1. 1. 1 ©2016 Acquia Inc. — Confidential and Proprietary Chris Urban Manager, Professional Services Large Scale Drupal Projects Successes & Challenges
  2. 2. 2 ©2016 Acquia Inc. — Confidential and Proprietary – Introduction and Background – Walkthrough notes from many large-scale projects – Compare challenges and solutions – Review of Lessons learned Agenda
  3. 3. 3 ©2016 Acquia Inc. — Confidential and Proprietary General Assumptions – Agile Workflow – Iterative development – Scrum or standup – Boards and tickets – Grooming – Planning – Process Management – Scrum Master – Project Manager – Project Evolution – Updates to documentation – Evolving process
  4. 4. 4 ©2016 Acquia Inc. — Confidential and Proprietary – Multiple initiatives – Multiple partners and/or globally distributed teams What makes a project “large scale”?
  5. 5. 5 ©2016 Acquia Inc. — Confidential and Proprietary Multiple Product Owners
  6. 6. 6 ©2016 Acquia Inc. — Confidential and Proprietary Multiple Stakeholders
  7. 7. 7 ©2016 Acquia Inc. — Confidential and Proprietary Getting to be more Agile – Consider Agile workshops – Practice writing user stories – Use sub-tasks and tasks for reminders and non- development based tasks
  8. 8. 8 ©2016 Acquia Inc. — Confidential and Proprietary8 ©2016 Acquia Inc. — Confidential and Proprietary Regular communication is a key for a successful project
  9. 9. 9 ©2016 Acquia Inc. — Confidential and Proprietary Communication/Process – Start with an Agile Workflow and Process – How much is too much? – Additional ceremonies – Release Planning (Product Backlog Refinement) – Backlog Pruning
  10. 10. 10 ©2016 Acquia Inc. — Confidential and Proprietary Development Workflow – Clear roles and ownership of states are defined – Changes accounting for BBD testing – Additional states/transitions for larger clients needed
  11. 11. 11 ©2016 Acquia Inc. — Confidential and Proprietary Daily Scrum – Worked on, Working on next – Blockers, requests for Discussions – Work/life balance or Temperature score – Larger groups = longer standup calls – Automate and focus on what’s important
  12. 12. 12 ©2016 Acquia Inc. — Confidential and Proprietary Sprint Planning – Serves as marker in time and common starting point – Sprint Priorities – Key Feature Summaries – Measure Results absolutely
  13. 13. 13 ©2016 Acquia Inc. — Confidential and Proprietary13 ©2016 Acquia Inc. — Confidential and Proprietary Good Team Management is a key for a successful project
  14. 14. 14 ©2016 Acquia Inc. — Confidential and Proprietary Working with delivery teams – central ticketing if possible is ideal – creation of tickets in JIRA via email – creation of tickets in JIRA in Slack or HipChat
  15. 15. 15 ©2016 Acquia Inc. — Confidential and Proprietary Working with Continuous Delivery teams – use a Maintenance backlog team – use a UX bugs and issues team – have developers contribute to a developer backlog and groom and pull in tickets
  16. 16. 16 ©2016 Acquia Inc. — Confidential and Proprietary Working with Support teams – Use as infrastructure resource – Accommodate Server upgrades and 404 mitigation
  17. 17. 17 ©2016 Acquia Inc. — Confidential and Proprietary17 ©2016 Acquia Inc. — Confidential and Proprietary Documentation: takes emotion out of the equation
  18. 18. 18 ©2016 Acquia Inc. — Confidential and Proprietary Documentation – Team Contacts and Developers Roster – Sprint ceremonies – RACI – Top level process workflow & expectations – JIRA Workflow and transitions – Spikes vs Tracer Bullets – Hotfixes – Developer documentation
  19. 19. 19 ©2016 Acquia Inc. — Confidential and Proprietary Documentation and Process Tips – Confluence – Google Drive – JIRA
  20. 20. 20 ©2016 Acquia Inc. — Confidential and Proprietary20 ©2016 Acquia Inc. — Confidential and Proprietary If the only tool you have is a hammer, you tend to see every problem as a nail.
  21. 21. 21 ©2016 Acquia Inc. — Confidential and Proprietary Project Level Tools – Google Docs – Confluence – JIRA – GitHub Wiki, Other wikis – Excel, Powerpoint – Email, VOIP – Chat: – Skype – Slack – HipChat – Others: Ryver, Fleep – screenshare/conf call software: – join.me – GoToMeeting – Webex – Zoom
  22. 22. 22 ©2016 Acquia Inc. — Confidential and Proprietary Development & Sprint Tools – Planning: – Aha! – Asana/Instagantt – Pointing poker – pointingpoker.com – play.planningpoker.com – Charting - Visio, Omnigraffle, draw.io – Whiteboard - awwapp.com – Acquia Dev Desktop
  23. 23. 23 ©2016 Acquia Inc. — Confidential and Proprietary Different tools for different teams? – How are tools used differently with multiple teams/groups/multiple partners? – scheduling – language
  24. 24. 24 ©2016 Acquia Inc. — Confidential and Proprietary Worst case scenarios – Sudden client staff changes – Key personnel staff get sick/hit by bus at same time – Client apathy – Client not able to make timely decisions
  25. 25. 26 ©2016 Acquia Inc. — Confidential and Proprietary – Successful teams communicate regularly – Successful teams know who is responsible for what – Successful teams know where to look for answers What did we learn?
  26. 26. 27 ©2016 Acquia Inc. — Confidential and Proprietary Thank You

×