When writing the title of this post I started to sing “How low can you go…How low can you go?” I told you that so I am not the only one with that song stuck in my head.
On to the blog post. Yesterday, I had a meeting with the technical lead for the project I am working on. We were reviewing some of the initial requirements I had elicited and we started discussing technical design considerations. He asked if I would be documenting some of the technical design details. My initial plan did not have me going that far, but I said I could and would if necessary. In the end, it was agreed he was the most qualified to document the technical requirements for the project.
Now I have a few questions. How technical do you go? Does your current role require you to work on the detail technical requirements for a project. If asked, could you go technical? Do you feel it is best for the business analyst to go technical?
Whether you do or don’t go technical, I feel it is critical for the business analyst to be part of the design sessions to ensure the business needs are being met through the designed solution.
Please share your thoughts. Thanks
- #AskAnAnalyst Podcast Episode 27: Remote Agile Team Success - March 23, 2017
- #AskAnAnalyst Podcast Episode 26: Are BAs Becoming Obsolete? - February 28, 2017
- #AskAnAnalyst Podcast Episode 25: State of Agile - February 7, 2017
- #AskAnAnalyst Podcast Episode 24: An Agile Mindset - January 27, 2017
- A Monthly Guide to Becoming a Better Business Analysis Professional - January 11, 2017
- #AskAnAnalyst Podcast Episode 22: Business Analysis in 2017 - January 10, 2017
- #AskAnAnalyst Podcast Episode 21: Business Analysis in 2016 - December 8, 2016
- #AskAnAnalyst Podcast Episode 20: Effectively Give and Receive Feedback - November 15, 2016
- #AskAnAnalyst Podcast Episode 19: Live from #BBCCon - November 3, 2016
- #AskAnAnalyst Podcast Episode 18: More Business Analysis Basics - October 4, 2016