Excellent video! I cannot underscore how important identifying dependencies, hidden requirements, and impacts of change at any early stage in the development cycle. It avoids a lot of technical debt and reputation risk.
Thank you for your delightful insights. I find your HR software example a little confusing. In Agile development, we don't just populate backlogs with business needs but with elicited needs. I begin with a "Context Diagram" that guides me to stakeholders I must collaborate with when collating requirements. It also helps determine the 'problem scope'. Together, we ascertain the technical feasibility of the "proposed solution" within the context of the business requirement in a brainstorming session held with those stakeholders and the IT team. The output of that JAD session populates my "Product Backlog". Business needs/requirements are "preliminary/potential backlog items" and not primary product backlog items ready for development.
I'm very glad you wrote this Katey. This mirrors the process I follow quite closely, and it mitigates much of the risk that I talked about in the video. I try to encourage my clients to allow for the time and resources needed to design the solution with this level of rigour, but many organizations lack the discipline and process maturity needed to do so. The fact that you see this as standard practice means that you're well ahead of many organizations.
Take the first step to becoming a high-performing business analyst ⇨ bablocks.com/membership/?ref=2
Excellent video!
I cannot underscore how important identifying dependencies, hidden requirements, and impacts of change at any early stage in the development cycle. It avoids a lot of technical debt and reputation risk.
Interesting 🤔. I’ve been looking forward to hearing you talk more about the product backlog. I’ll definitely be there for the live.
Great. Looking forward to seeing you there.
Thank you for your delightful insights. I find your HR software example a little confusing. In Agile development, we don't just populate backlogs with business needs but with elicited needs. I begin with a "Context Diagram" that guides me to stakeholders I must collaborate with when collating requirements. It also helps determine the 'problem scope'.
Together, we ascertain the technical feasibility of the "proposed solution" within the context of the business requirement in a brainstorming session held with those stakeholders and the IT team. The output of that JAD session populates my "Product Backlog". Business needs/requirements are "preliminary/potential backlog items" and not primary product backlog items ready for development.
I'm very glad you wrote this Katey. This mirrors the process I follow quite closely, and it mitigates much of the risk that I talked about in the video. I try to encourage my clients to allow for the time and resources needed to design the solution with this level of rigour, but many organizations lack the discipline and process maturity needed to do so. The fact that you see this as standard practice means that you're well ahead of many organizations.
Great insights and very well laid out!
Great please upload more videos