Year of the Mashup!
From the Drunken PM Blog
by Dave Prior
Drunken Boxing for Project Managers
“The main feature of the drunkard boxing is to hide combative hits in drunkard-like, unsteady movements and actions so as to confuse the opponent. The secret of this style of boxing is maintaining a clear mind while giving a drunken appearance.”
Yeah... just like that… but with network diagrams and burndown charts… and a wee bit less vodka.
Recent Posts
Certified Agile Leadership Training with Olaf
Don Kim - I Think, Therefore I Plan
Agile Coach to Agile Gamer - Peter Saddington
Scrum in School - A Case Study of Grandview Prep's Transformation
Forecasting Tools Based on Team Performance with Troy Magennis
Categories
20 Hour,
211,
4-Hour Body,
4-Hour Chef,
4-Hour Work Week,
Aakash Srinivasan,
Aaron Smith,
Adam Weisbart,
Adrian Howard,
Agile,
agile digitalpm,
Agile 2010,
agile 2015,
Agile Alliance,
Agile Classroom,
Agile Enterprise,
Agile Mindset,
agile reporting,
agile transformation,
Agile Tribes,
agile2015,
AgileClassroom,
AgileCraft,
AgileScout,
AgileThinking,
Ainsley Nies,
Al Goernor,
Al Shalloway,
Alistair Cockburn,
Angela Harms,
Anna Beatrice Scott,
Ansley Nies,
AOW4PM,
apocalypse now,
apple,
art of war,
Bas De Baar,
Bas Vodde,
Beyond Legacy Code,
Big Visible,
BigVIsible,
bimodal,
Blackie,
Bob Sarni,
body language,
book review,
braintrust,
branding,
breaking gantt,
Brent Beer,
Brett Pohlman,
Brian Bozzuto,
brian flatow,
brian rabon,
business agility,
Business Model Canvas,
CAL,
Canvas,
capacity,
carson pierce,
Catherine Louis,
Center for Non-Violent Communication,
Certification,
Certified Agile Leadership,
certified scrum trainer,
Charter,
Chet Hendrickson,
Chris Li,
Chris Spagnuolo,
Christine Neidhardt,
cloud,
cloud worker,
co-working,
Coach's Clinic,
Coaching,
cochlear,
commitment,
conteneo,
Corkulous,
coworking,
Craig Larman,
Crystal,
CSM for PMP,
cst,
DAD,
Dan Brown,
Dan Greening,
dan markovitz,
data,
Dave Prior,
David Anderson,
David Bernstein,
David Bland,
David J Anderson,
Dean Leffingwell,
Dean Stevens,
Declan Whelan,
Denise Jacobs,
Dennis Stevens,
Designing Together Design,
Dhaval Panchal,
diana larsen,
Digital Pm Summit,
Digital Project Management,
digitalpm,
Disciplined Agile Delivery,
Distributed Teams,
Docs to Go,
Don Kim,
dpm,
dpm2013,
drunkenpm,
drunkenpm radio,
eduscrum,
Eight Shapes,
Elizabeth Harrin,
Elizabeth Hendrickson,
Elizabeth McClellan,
EMEA,
emotional intelligence,
Enterprise Scrum,
Essential Scrum,
esther derby,
EVEF,
Evernote,
Every Voice Engaged,
Experience,
Explore It!,
facebook,
field guide,
FIRM REPORT,
First 20 Hours,
Flight Levels,
Flipboard,
FocusedObjective,
forecast,
Forecasting,
Frank Illenberger,
Fred George,
fred kluth,
funny garbage,
Gil Broza,
Github,
Global Economics,
Grandview Prep,
Greg Balestrero,
GTD,
Happy Cog,
Heartline,
Howard Sublett,
hybrid,
I Think Therefore I Plan,
Iain Frasier,
ICAgile,
Idea Wallets,
improvisation,
InfoQ,
InspireMe!,
International Consortium for Agi,
IOS4,
iPad,
iPad 2,
iPad2,
iPhone,
IT&T SIG,
J.B. Rainsberger,
James Tamm,
Jason LIttle,
Jean Tabaka,
Jeff Patton,
Jesse Fewell,
Jessica Kerr,
Jessie Shternshus,
jim benson,
Jim Tamm,
johanna rothman,
John D Cook,
john miller,
Judith Lasater,
Jutta Eckstein,
kamal manglani,
kanban,
kanbanfor1,
kanbanpad,
Kate Sullivan,
Kathy Compton,
Ken Rubin,
Ken Schwaber,
Kenny Rubin,
Keynote,
Kuala Lumpur,
lacey,
Large Scale Scrum,
Larman,
Larry Maccherone,
Larsen,
Lasater,
Leadership Meeting,
LeadingAgile,
lean,
Lean Kanban University,
Lean Systems Engineering,
LeanKit,
Leffingwell,
LESS,
Liftoff,
Linda Rising,
Lithespeed,
Livescribe,
Livescribe Pulse,
LSE,
Luis Garcia,
luke hohmann,
lyssa adkins,
Mac,
MacWorld,
Macworld 2011,
Magennis,
Malaysia,
Malaysia Scrum User Group,
Management,
Managing the Unmanagable,
Manny Gonzalez,
Marc Johnson,
Marshall Rosenberg,
Martin Rosenqvist,
mashup,
matt barcomb,
MDEC,
Merlin,
metrics,
Michael Sahota,
Michele Sliger,
Mickey W. Mantle,
Mike Cohn,
Mike Cottmeyer,
Mike Sutton,
Mike Vizdos,
mitch lacey,
MITPM,
Mode 1,
Mode 2,
modus cooperandi,
Modus Institute,
Nanette Brown,
Natalie Warnert,
Nic Sementa,
NLP,
Non Violent Communication,
Non-violent communication,
Notes Plus,
NVC,
off shore,
Offshore,
Olaf Lewitz,
Open Space,
Oredev,
Øredev,
oredev 2013,
organizational agility,
Organizational Change,
overcommitment,
pag,
Panda Transport,
Panel Picker,
Papershow,
Paul Hammond,
personal agility canvas,
personal branding,
personal kanban,
personal productivity,
personal project management,
personal projectmanagement,
Peter Saddington First15,
Petra Goltz,
Philamade,
pk,
Planning,
PM4Girls,
PMI,
PMI Portugal,
PMP,
podcast,
Product Owner,
Product Ownership,
productivity,
Project,
project management,
project manaqement,
project planning,
Project Potion,
Projects At Work,
projectshrink,
ProjectWizards,
Projet Chartering,
pulse,
rachel howard,
Radical Collaboration,
reach the peak,
Rebecca Wirfs-Brock,
review,
riaan rottier,
Ricardo Vargas,
Robyn Meredith,
Ron Jeffries,
Ron Lichty,
Rosenberg,
SAFE,
Safety,
Sam Barnes,
Sanjiv Augustine,
Scaled Agile Framework,
Schneider and Associates,
School of Rock,
Scott Ambler,
Scrum,
Scrum Alliance,
scrum but,
scrum field guide,
Scrum Gathering,
Scrum in Education,
Scrum in Schools,
scrum in waterfall,
ScrumFest,
Shane Hastie,
Showing Up,
SK Khor,
social media,
SolutionsIQ,
sprint planning,
Steffan Surdek,
stephen denning,
Steve Elliott,
Stewart Copeland,
Story Mapping,
Sun Tzu,
Swarming,
SXSW,
SXSW2012,
Tabaka,
Team Performance,
Teams,
Telecommunications,
Telepresence,
Temenos,
Test Obsessed,
the adstore,
The Ron,
theStrayMuse Louder than Ten,
Thierry Holoweck,
Things,
Thushara,
Tim Ferriss,
Tim Ferriss Experiment,
To Be Agile,
Tobias Mayer,
Tom Kealey,
Tom Mellor,
Tom Perry,
Tom Smallwood,
Tribes,
Tricia Broderick,
troy magennis,
TrustTemenos,
twitter,
Unicat,
User Stories,
value,
VCP,
video conferencing,
Virgin Digital,
Vivek Angiras,
VLC,
vocal technique,
waste,
Weisbart,
What We Say Matters,
Wijewardena,
WIzewerks,
Woody Zuill,
WWDC,
yellowpencil,
Zeldman
Date
My New Year's Resolution A few weeks ago I was at
P2P in Cairo, speaking with Philip Diab, the 2008 Chair of PMI. We were both about to give brief speeches at a conference and he brought up the idea of developing a consistent theme and using it as a sort of guiding idea when preparing for presentations over a period of time. It was great advice, and I have decided that I am going to start off by applying it to the blog.
Remix In Lawrence Lessig's new book "
Remix", he devotes a fair amount of time early on, to explaining how kids today are creating mashups with music and he goes on to detail what the legal ramifications are with this and the book goes on from there. If you like Lessig's work, or are at all into reading up on copyright law and intellectual property rights, I highly recommend it.
While I was reading it, I found that I kept drifting back to the idea of mashups and other places that they occur in modern life. The basic premise is that you take two existing things and push them together to create something new and (ideally) better. The site
Mashuptown.com has a great video explanation of it in the upper right corner of their homepage.
Depending on your taste in music, this could be a good or a bad thing. But, in coming back to it, I started to think more about the other places in my life that this takes place - especially work.
So, jumping back to the whole consistent theme thing... for 2009 my focus is going to be on PM Mashups, or, bringing different (pm related or not) ideas and practices, etc., together in one's approach to project management with the end goal of coming up with a more cohesive, adaptive and ideally, creative way of managing work. My plan is to develop a series on the idea and hopefully, I'll be able to find a bunch of folks along the way who are also mixing their chocolate and peanut butter and don't mind talking about it.
PM Mashup #1 For about 18 months I have been primarily using
Scrum to manage my projects. For most of what I do, it works very well. It's adaptive, lightweight, and is great for developing trust with the clients. However, I have found that it for it to work best, I need to add some components from other approaches.
Traditional
PMBOK type documentation is something I tend to get lazy about, so I am always trying to find ways to make it easier to get through. I do, however, think it is critical to have those artifacts and I am a very firm believer in keeping a historical record so that you can learn from your mistakes. It would be easy to get away without doing this in Scrum, but, as I mentioned above, I think that historical artifacts are critical and, even if there are no defined requirements at Go, I do think that they need to be locked down by the end of the project. (Always leave the room nicer than you found it.)
So now, when I'm working on Scrum projects, I generally try to make sure we have a wiki set up so that we can provide the client with documentation that will be current by the time we leave and which they will hopefully maintain as a living, organic version of the requirements doc. Now, I know that the requirements doc should be created up front, but the simple fact is that most of the time, what is being asked for initially, is not entirely definable and will probably change during development. I also know that once we create the initial requirements that I, as the PM am responsible for keeping it current. Unfortunately, in practice, what I've found is that the requirements doc becomes something that is either A) gathering dust the moment it leaves the printer or B) something I work furiously on updating so that it can gather dust the moment it leaves the printer.
My goal is to have a place to capture whatever we initially know in an informal, plain language manner and then build on it as we move forward. We usually start out by entering whatever use cases we have and we work with the product owner until they reach a level of comfort entering directly into the wiki themselves. Over the development cycle, the use cases are updated by the team as they evolve into a sort of post development explanation of what is in place. We evolve, with the product owner, from the initial need, to the realized product, which is documented in plain, simple language. It is not traditional requirements and may lack a lot of the structure that a traditional requirements doc includes, but if the objective of the traditional requirements doc is to define what is requested to a level of detail that can be executed and litigated against, then the wiki reqs, or Requirements 2.0 is intended to be easily digested by humans who may have a need for the information.
This mashup doesn't fit perfectly into Scrum or a PMBOK type approach. But, it does enable the workflow process and meets the informational needs of the client in a way that does not place an undue burden on the team.
I'll post more in about a week, but if you have any mashups of your own, I'd love to hear about them.
Happy New Year!
Posted on: January 02, 2009 09:29 AM |
Permalink
Comments (1)
Please login or join to subscribe to this item
Kwiyuh Michael Wepngong
Community Champion
Financial Management Specialist | US Peace Corps
Yaounde, Centre, Cameroon
Yes, it's always about finding new ways
Please Login/Register to leave a comment.
|
"The purpose of art: to make the unconscious conscious."
- Richard Wagner
|
