According to Leisa, they are: small teams, motivated people, limited planning, minimal scope, small projects, rapid release, responsiveness, and iterations. Leisa noted that the essential point of her presentation was that “there are other ways to manage projects than ye olde fashioned waterfall methodology.”
I use the term Project management 2.0 to describe an evolution of project management practices inspired by Enterprise 2.0 tools. Traditional project management software implies project manager acting as a proxy in all project related communications, thus reducing productivity of project manager and the rest of the project team. New tools bring collaboration into the planning process, making the team much more productive and changing not only the technology, but process as well.
Over the past two years, IBM has been busily launching in-house versions of Web 2.0 hits. “We’re trying to see how things that are hot elsewhere can be fit for business,” says Irene Greif, an IBM Fellow who heads up Collaborative User Experience.
While fundamentally true the missing link is not considering the adoption of social tools as a means to transform operations, culture and customer interfaces. The other misunderstanding is the value to internal resources learning how to use the tools to transform the culture into an ongoing quest for Socialutions for all stakeholders benefit.