My Daily Thoughts


Future State Deliverables

You can't connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something - your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.
Steve Jobs

Before you can determine what the deliverables are for a future state you need to ask the question of why is the future state being created and who is creating it.

Is a new application being installed?
Is business looking at improving processes?
Is there an issue that needs addressing?
Who is involved in creating the future state?
What experience and tools do those involved have?

All of these could be valid reasons for doing a current state analysis.

Some of the deliverables that could be produced are:

  • Process diagrams
  • Data models
  • Business Rules
  • Roles
  • Business Needs
  • Prototypes
  • User stories
  • Use cases
  • State diagrams
  • Wireframes

Which deliverables will best help with the change that is being contemplated? What form will the individual deliverables take to support the change? Who is involved and whare are their experiences? These are all questions a business analyst needs to ask.

Will the change be created in an agile way or a structured waterfall way or a hybrid way? Is the change being done in-house or outsourced? How well will the change be received?

These are all questions to help figure out how to create the future state successfully.

No two future states in different organizations will be created in the same way.

Live the Adventure


Share this post

Leave a Reply

Your email address will not be published. Required fields are marked *