Your new post is loading...
With Agile delivery, we trade big upfront design for a “just enough” approach. But how do we make sure we get the right MVP?
|
Scooped by Victor Jimenez |
Scoop.it!
No comment yet.
Sign up to comment
Successful projects with important lessons to share are not always the result of superb communication and disciplined documentation to capture all insights learned along the way. In fact, sometimes a project is successful simply because of the sheer determination and brute force put in by a few key personnel who overperform to achieve the project deadline and promised performance standard. The Agile approach intends to break us from this mindset of work that requires overperformance in order to achieve performance goals. Approaching work with Agile in mind allows teams the permission to revise their assumptions as they proceed and to make better decisions in pursuit of the project goal. The ability to observe and reassess per increment means you have to collect insights and discuss along the way. Immediately, the characteristics which define agile project success are more defined by inculsiveness and awareness rather than isolation to make a concentrated effort and a reliance on sticking with the plan.
I've been looking for a KM body of knowledge for a while and settled on just cultivating my own through practical application. Agile concepts seem to be the best reservoir of active knowledge to draw upon. With that said, I encourage others to find and share other sources for best practices in Agile project management application. I believe Agile is a magnifier of organizational learning through it's ability to produce high quality knowledge artifacts and empower Knowledge Managers to spend their time curating and connecting others to a central library of insights gained.