The definition the latest BABOK has for Plan and Change centric project delivery methods is very useful. It's not exactly ground breaking to break methods/processes into different camps based on whther they are Agile or Waterfall - but the terms are pretty loaded. I think these terms capture the essential differences between these two camps.
It's not that one camp has different component tasks, it's just that one puts the plan as the central tool for delivering change, the other puts the change being delivered at the centre of planning.
You see this really clearly in the way that BABOK 2.0 describes the Requirements Anlysis tasks. The same basic activiteis are always done, but how and when they are done changes depending on process.
It's just nice to have a neutral non-emotive term.
It also reinforces that good BAs are good BAs regardless of methodology. If you know how to do it right for Waterfall you're going to be able to hit the ground running with Agile. The hardest bits don't change. Empathy, communication, listening, lateral thinking, modelling, and problem solving are always the core-skills.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment