Remember, requirements are the what but not the how. And it’s our job as business analysts to help our clients remember that what we really need to understand is their what, and that it’s our job to find the how.
But sometimes you have to remind them of that.
And sometimes it takes 28 times.
Three things to consider when preparing for modifications to an existing system.
Whew! This year has started off with a bang! Kicking off a large, strategic project has been refreshing – and has reminded me of some important lessons. So I thought I’d share 5 things I was reminded of over the past couple weeks and to get your thoughts on what I have coming up next.
Preparing the Requirements Work Plan gives you a chance to take a step back, analyze the scope of work, and determine the best techniques and approach to facilitating the requirements work.
So, we’ve had the Project Kick Off and now it’s time to start digging in to those requirements, right? Not quite yet. While the Project Kick Off sets the overarching framework of what to expect, the Requirements Kick Off prepares stakeholders for what is happening right now.
How do you define requirements? A large portion of our job is learning, understanding and communicating requirements. But what are they exactly? If we don’t know how to easily define it, how will we know when we’ve got it? And how will we explain to our clients what we’re looking for? Requirements are…