Year of the Mashup!
| 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! |
Updates... finally
| > New Podcast Videos have been posted to the IT&T SIG iTunes Podcast and Vimeo It has been awhile since I've posted anything, but things are almost settled down and I am hoping to get better about that in the coming weeks. While I was in Warsaw I had a chance to shoot interviews with the PMI Poland Chapter President, Rafal Mielczarek and Andy Brandt from Codesprinters. (I am a huge fan of Banana Scrum.) Since my last post from the PMI Poland Chapter's 3rd Annual Congress in Warsaw I have been traveling a bit. I was fortunate enough to be able to present at Øredev 2008 in Malmo, Sweden. It was one of the best conventions I have ever been to. The cross section of developer, project managers and tech geeks from all over the IT space made it an event that I'll probably be measuring every convention I go to from now on. The variety of ideas shared was what made it such a rich learning experience. Everywhere I went there seemed to be some kind of debate going on and everyone there was completely passionate about their craft. Getting to meet Diana Larsen and Jeff Sutherland was very cool. I also had a chance to shoot a video interview with Gabrielle Benefield, which you can see if you follow the Vimeo link above or check out the IT&T SIG Video Podcast in iTunes. |
If it's Monday, this must be Warsaw
| Greetings from Poland! I still have a lot of updates to post from Denver, and a slew of great video, but between trying to catch up from being away, watching the Phillies restore my long lost belief in Philly sports teams and getting ready for Warsaw... I'm still working on catching up. Right now I am in Warsaw at the 3rd International PMI Poland Congress. Things got off to a great start this morning and I am truly honored to be here. Rafal Mielczarek kicked things off this morning with an introduction that set the tone for what promises to be two days of great networking and learning. Just a few highlights... The Poland Chapter is something of a star in the PMI world, due to its very successful implementation of the Chapter with Branches model. They've done so well that the PMI Poland chapter has grown to 500 members since it received it's charter from PMI just five years ago, and this includes 25% growth just since the summer. As Rafal jokes, as the Dow goes down, their membership goes up. In the first session, Alexandre Rodrigues, gave a presentation called Dynamic Risk Management. It covered all the basics of Risk Management and then launched into some very detailed explanations of the different tools, how they work, etc. In his talk, he urged the group to approach at Risk Management from a mindset that would allow them to see the opportunities as well as the negatives. He went on to recommend doing all they could to become aware of the opportunities and learning how to take advantage of them. My favorite line was when he said, "The project is not for the project, but for the business results." I think we (PMs) often lose sight of that when we are in the thick of things. He also explained to the participants why you can't manage risk my responding to deviation, but rather, you need to take action before the deviation occurs. I'll try to post something again this evening. I'm also going to be posting to the IT&T SIG Twitter Feed (http://twitter.com/pmiittelecom) Right now I have to get back in there because I'm missing Alfonse Bucero's presentation on How to Upgrade a Weak Project Culture. Before I go, I do want to say a special thanks to Kamila Siebierwska for all her help while I was preparing to come to Warsaw for the Congress. She’s been a great help! |
PMI 2008 North American Leadership Institute Meeting - Day 1
| I’m listening to Mark Mulally’s Keynote presentation for PMI’s 2008 North American Global Congress. The work that he, and others, have been doing for the past year is a critical part of making the case for why project management is needed and what value it can provide. This Leadership meeting is probably going to be one of the most important sessions that has been held for the SIGs and Colleges. The state of the Virtual Communities Project, and what impact it will have on SIG/College communities is probably going to be the main discussion topic in the sessions and the halls here at the Denver Convention Center. As for what this will mean to IT&T SIG members, I’m going to try and hold off on commenting until the sessions are complete… the key word being try. We’ve got a lot of great things happening on the SIG website that all focus on keeping our members up to date on what is happening in Denver. We will be posting video podcasts every day, blog updates, twitter feeds and flickr feeds the whole time we are here. On Monday evening we will hold our Annual Member Networking event. It is something I always look forward to because it gives us the best opportunity we have all year long to sit down with our members and the friends of the IT&T SIG and find our how we are doing. Each year, the feedback has helped us drive forward with new projects and programs that, hopefully, add to the member value we are providing. And without a doubt, the part about this week that I am most excited about is our event on Saturday night where we will co-host a reception with the Scrum Alliance to promote the work we are doing with them. We’ve been getting a great response to our Scrum webinars and we have even greater things in store for next year. This is going to be a very exciting week. |
Updates....
| It has been awhile since I posted anything, but a lot has been going on. I’ve been working on preparing for PMI’s Congress and the other events happening this fall, as well as the project that the IT&T SIG is doing with the Scrum Alliance. So far we’ve held four webinars with the Scrum Alliance and they’ve gone quite well. We’ve had good attendance and great questions. There will be another one this coming Tuesday at 8 PM Easten and the beginning on October 7 we will switch to a 12 Pm Eastern start so that we can make the calls easier for our friends in the EMEA region. I’ll be posting a listing of events that the SIG is putting on in Denver and beyond sometime over the weekend. In the meantime, if you are planning on attending the PMI Congress, will be there on Saturday night (10/18) and find yourself often waking in the week hours, in a cold sweat because you can’t stop thinking about how to make Scrum and traditional project management work better together, please send me an email and let me know ([email protected]) we’ve got something in the works you might like to get involved with. |





