Drupal developer Jacob Rockowitz recently posted a blog series on Good Drupal Leadership. While this series does mention some things specific to Drupal and the Drupal community, it's actually an excellent general overview for any large software implementation project, including the types of group projects found in CIS-294.
Good Drupal leadership needs to:
- Help define and evolve a plan and strategy for implementing Drupal.
- Guide the process and best practices for building and maintaining a Drupal website/application.
- Organize the people and resources required to do the work.
- Build the relationships within an organization and the Drupal community.
There’s a lot to discuss here, and some of these tasks could create or change roles within an organization. It's worth breaking down these discussions into smaller blog posts. In my next few blog posts about good Drupal leadership, I’ll begin to answer the questions below.
- Part 2: What’s a good plan for implementing a Drupal website/application for organizations?
- Part 3: What is the process for organizations building and maintaining a Drupal website/application?
- Part 4: What are the resources an organization requires to build a Drupal team?
- Part 5: What are the relationships an organization needs to build to succeed with Drupal?
- Part 6: What miscellaneous skills does an organization's Drupal leadership need?
I highly recommend reading Jacob's series to get an overview of what you'll encounter during your semester in HFC's Software Engineering class. The posts are short and should only require 15-20 minutes to read the entire series.