Agile was born out of a conversation about what works well in software development. It wasn’t meant to be a dramatically “new” way of working. In the context of requirements, embracing agile empowers teams to focus on business value, user experience, and empathy, and...
Dead air and chirping crickets–is that what you hear when someone asks a question during virtual meetings? It’s frustrating for the facilitator and the participants! How do you get people to participate? How do you get what you need from shy (or...
“Requirements take too long!” That’s the message I am hearing from organization leaders across the country. That sentiment leads directly to pressure on BAs to get requirements done faster. Unfortunately, the most common strategy to speed up requirements is actually...
What can BAs and Agile Product Owners learn from Design Thinking and User Centered Design? It’s not all about UX and UI! It’s about the customer journey and the end-to-end customer experience with the organization or process. It’s about seeing the...
An agile BA practice is part of, and an extension of, the product ownership team. The BA practice helps the team build the RIGHT product and features, in the most valuable order, aligned to the organization and product strategy. BAs ensure the RIGHT features are built...
Tight timelines put pressure on the entire project team. When the project plan dictates unreasonable durations, BAs become document dispensers focused on cranking out BRDs or cramming user stories into JIRA. PM pressure often forces BAs to focus on documents instead...
