What should you do first? Would you define your requirements scope before you start to identify and analyze your stakeholders or vice versa? Would you receive the same answer if you asked 10 Business Analysts? I would bet not. Many might answer that they identify scope first before they can identify requirements stakeholders. Others would start with the people whom they know are impacted by the project.
Does it matter which is done first? Probably not and I will tell you why. Typically you want to start with what you know most about the project. As a Business Analyst I continually ask myself two questions: what do I already know and what is most important to know next? Most project activities do not happen sequentially, especially during the planning process. It really doesn’t matter which activity you do first as long as you focus on defining what you need to know most at the appropriate time on the project. In the beginning of the project you will want to understand the breadth of the project based on some key elements such as the scope and the stakeholders-and it really does not matter where you begin.
- Being part of the solution - May 1, 2012
- What’s the difference between ordinary and extraordinary… - March 14, 2011
- Lots of resources to learn about agile - May 10, 2010
- Agile and the BA – Part 1 - March 23, 2010
- Is It Really Tyranny of Best Practices? - February 20, 2010
- BAs are Bridge-Builders Instead of Bridges - January 25, 2010
- James Bond and Business Analysis - January 18, 2010
- Should the BA scribe at a team meeting? - August 4, 2009
- Why do we need detailed business requirements? - July 28, 2009
- Updated CBAP® Handbook now available for download - July 14, 2009