project management

Below is a recap of the discussions had at my PM BoFs in Munich this August 2012, and the resources we talked about. Thanks to everyone who came and participated!

As is the case with most of the PM BoF’s I’ve done over the past 4 Drupalcons, the conversation I was most interested in was around lessons learned. I love it when people can discuss where their projects went off the rails, why, what drives them crazy and how we can all learn from those experiences and exchange ideas/solutions.

I recently posted about how sad kitteh I am to see no action on this group.

Here are 10 quick/easy things we can do to change this:

1) Share PM articles to create a cool library of info
2) Share PM podcasts or videos to add interactive media to the mix
3) Ask our PM questions, like "Anyone know how to convince a client NOT to do fixed scope/fixed bid?"
4) Write articles about your PM experiences
5) Share your favorite PM tool & why
6) Ask if anyone has experience with "XYZ" methodology, tool or situation to start up a convo

Just posted this, reposting here so it gets Drupal-PM attention :)
Please let me know what you think, do you want it or not? If enough interest I'll keep pursuing creation of a PM-day pre-con.

http://www.bluesparklabs.com/blog/do-you-want-pm-day-drupalcon

Hi Guys,

While I was entertaining the relatives this weekend, I couldn't help thinking about Drupal. It's a sickness really. I need to seek help. Before I do though, I wrote this blog post on the key areas I feel need to be explored before taking on a Drupal project. As we all know, some projects are bad bad bad. Some projects are really good. Going through this long rant list that I've compiled should give the new folks the benefit of what some of us older guys have already suffered. It's on my blog here: http://www.drupalcreations.com/blog/drupal-specifications Please feel free to disagree and comment in sarcastic and critical tones. Ideally we get a thread going and share some of the wealth.

I'm off to seek help now :) ,

I've found there's one common mistake that I've made as a Drupal developer/Consultant, time and time again: project management. I wrote a short blog about my learning experiences here: Project Management If you're new to the world of professional Drupal consulting, read it to prepare yourself. If you're old, please add some comments to help new recruits understand the value of working a plan.

I give some real world scenarios as examples of mistakes that I've made. It should illustrate why it is critical to follow every step of the project management process. It'll help you avoid a lot of the pain that I suffered through.

For anyone new to the world of Drupal consulting, you should really read through this blog.

Good luck and May the force be with you,

In response to several posts in this group.

Telamenta is a South African based Drupal Company. We are 2 1/2 years old. I have many years experience in coding and project management. We have worked very hard over the last 2 years to optimize our quoting for clients. I play the role of scrum master and lead developer in the company. We use the following methodologies and tools.

Scrum
For agile development we use Scrum as a methodology.
Why?:

<

ul>