Summary : It’s obvious that in many cases traditional project management methods need to become more agile. That’s not without bringing new issues due to the need to keep eveyrone informed of the status of a project that is continuously being re-designed. Social media are very good at addressing the need of narating a project beyond the traditional quantitative indicators of traditional tools. But there’s still something missing in the enterprise social media offer : even if some niche players offer project socialization features, most of generalist social software vendors don’t while it would make a lot of sense next to the conversational spaces that are the heart of their product.
In more and more fields it’s becoming obvious that agile methods are becoming the most relevant to manage any project and this approach, that used to be restricted to IT projects is nom being used in more and more areas. The reason is quite easy to undersrtand : in a world where cycles are becoming shorter and shorter, plans that aims at delivering something in 2 or 4 years are not relevant. Proceeding step by step, having functional deliverables that comes progressively and continuously redesigning the project in order it meets actual current needs instead of delivering something that meets what was needed years ago but is irrelevant to the current context seems to be wiser and more efficient way of managing a project.
When, during a projet, some specific expertises and resources have to intervene on certain specific parts, it brings an added complexity. In a classical project, anyone knows what to do and when because the project follows a well defined path. In an agile project, where the roadmap and the specifications continuously evolves, resources are often lost because they don’t know how things have evolved from the original project. It’s a matter of awareness.

You can find the "original" french version of this blog here

