Showing posts with label ProjectsatWork. Show all posts
Showing posts with label ProjectsatWork. Show all posts

Wednesday, April 06, 2016

Catching Up... 27 Podcasts, 5 Blog Posts and a Chicken

Me holding a chicken
Sometimes, when you leave for the airport so you can go teach, you forget your guitar. (Actually, it isn't really a "sometimes" thing... more of a "once" thing... NEVER AGAIN).

When that happens you find yourself staring at your Kanban board looking at the cards that never move... like the one that says UPDATE YOUR BLOG!

I've been total crap at keeping this up to date. Sadly, my own blog is always the last place I remember to post new things, so... here is an onslaught of things  I have posted since the Agile 2015 Interviews.

I'm going to try (again) to suck a bit less at keeping this up to date.

If you like any of these, the best place to see updates from me on podcasts is on Twitter @mrsungo or @drunkenpm. (And there are some REALLY good ones coming.)

drunkenPM Radio Interviews (Episode 3 is coming soon)
Projects at Work Podcast Interviews
Note: these require registration, but it is free
LeadingAgile SoundNotes Interviews 
LeadingAgile Blog Posts  


Tuesday, April 24, 2012

Projects@Work White Paper - Distributed Agile Teams: Achieving the Benefits


ProjectsatWork has published a study called Distributed Agile Teams: Achieving the Benefits. The report was put together by Elizabeth Harrin  (@PM4Girls), who is the author of the website A Girls Guide to Project Management. The results of the research cover a lot of ground with respect to what makes distributed Agile projects work and what can contribute to their failure.  The report is very insightful and definitely worth the time it takes to read. While some of the findings may seem like common sense, knowledge workers in the IT space (myself definitely included) seem to possess a remarkable capacity for periodic loss of grip to that tether.

My favorite part comes at the very end during the summary of recommendations. Number One on the list is:
Don’t act like your project is co-located – pay the tax for distribution. 

This is one of the most simple things that so many of us forget when we are working at a distance. I believe this applies whether you are working down the hall from someone, or across the globe… there is a price that has to be paid when you are not sitting in the same room. With the transparency that Agile offers, this tax becomes far more obvious. There is no doubt that distributed teams provide a number of benefits, but those benefits come at a cost. The reason (IMHO) so many people struggle so much with distributed is that they keep thinking that the ride is free ... which it theoretically could be… unless you actually want it to work.