Client Area

Do Drupal Right

Blog
Thursday, July 12, 2012 - 9:03am

Managers and developers at some point in their career ask themselves, “Should I adopt the agile methodology?” I know it can seem a little scary to think about diving into this type of project process, especially for a project manager. However, agile done right can be a good process tool for a project manager, development team, client and ultimately the consumer.

I think there are misconceptions on what agile really is. Some people think that agile means constant change and endless budget—what team or client could possibly sustain this model? What agile means to me is a process used to understand and meet the client’s objectives. It is used to deliver features to consumers sooner, and it enables the development team to produce a better quality product.

Thursday, May 17, 2012 - 11:58am

With something as simple as the post title, I've already broken one of the rules I'll be setting forth here—that of expectation setting. This is not a post about ignoring your clients or putting them aside or picking only the right clients and shunning the rest. This real subject of this post is the '-tion' (pronounced shun) suffix at the end of the three key thoughts: communicaTION, expectaTION and execuTION.

Wednesday, February 15, 2012 - 5:20pm

OK, brace yourself. Let’s talk about the issue that inevitably causes everyone to become squeamish. Budget, hourly rate, time and material, fixed bid, etc. – you have heard the pricing terminology before.  It is no secret that Drupal and open-source in general has struck a positive chord with organizations of all sizes. Why? One undeniable factor is because it’s free – pretty cool, hey.  You can download, poke around, and tire-kick as long as you desire.  

Thursday, September 29, 2011 - 11:47pm

While preparing for the Drupalcamp Atlanta session that I will be presenting on Saturday with my colleague, Don VanDemark, it was necessary to take a step back and examine the step-by-step approach to tackling cases that we wanted to promote. Before I could get to the fun slides with photos of Smurfs and things, I took a look at the steps that might lead to the more consistent, predictable experience to which our team is always striving.

Tuesday, March 8, 2011 - 3:07pm

Greetings from DrupalCon 2011 at the Sheraton in Downtown Chicago. Mediacurrent has several team members in attendance, and we have a company information table setup at booth 31 in the exhibit hall if you want to stop by to say hello.

I'll be keeping a log of highlights from the sessions I attend each day during the conference. After Dries' keynote this morning that reviewed Drupal 7 and outlined plans for Drupal 8 process, Tuesday is starting with an overview of the Media module, followed by sessions about client and project management.

Media!

by Aaron Winborn & Jacob Singh

Sunday, January 16, 2011 - 3:44pm

This blog post is part of a series on Drupal distributions. The first post discussed the difference between distributions, installation profiles, and Features.

Drupal distributions are the foundation of what I like to call "Drupal as a product." Distributions are like pre-packaged websites: where Drupal core can be turned into any kind of website by configuring it and adding modules, distributions come pre-configured and with the modules needed for a certain type of website.

Wednesday, January 12, 2011 - 11:05am

With the last week's release of Drupal 7 and a steady stream of large enterprise sites continuing to migrate onto the content management platform, excitement abounds in the Drupal community. While celebrating all that is new, however, let's not forget about some of the early adopters that helped pave the way for all of the brand-name companies now hopping on board.

Friday, August 27, 2010 - 9:00am

This summer I was a mentor for the Google Summer of Code program for Drupal. I maintain the Facebook-style Statuses module, which allows users to have a stream of “status updates” on their user profiles and to write messages on other users’ profiles, like Facebook.

Friday, November 13, 2009 - 8:12pm

Drupal's multi-site feature makes it possible to significantly increase the efficiency of managing a group of similar sites.  Imagine you have a group of clients where each client owns a site within your multi-site structure.  Undoubtedly, many of them will want to take advantage of Drupal's ability to add new features, which makes sense.  But if you're not careful, you can find yourself in a nightmare situation caused by a perfectly reasonable business decision to implement what clients want, when they want it.  The purpose of this blog entry is to provide some best practices that will make managing this kind of system a rewarding experience for you and your clients:

1. Prohibit Site-Specific Functionality:

Tuesday, November 3, 2009 - 5:15am

Drupalcamp Atlanta Session Videos One of the over-riding goals of the Drupalcamp Atlanta organizers was to provide as much video footage of the event as possible in order to share back to the community at large.