Do Your User Stories Have a Happy Ending?
Starting your user story by stating the business goal/objective that you want to achieve simplifies the process of collecting and managing your product backlog.
Starting your user story by stating the business goal/objective that you want to achieve simplifies the process of collecting and managing your product backlog.
Well-structured, relevant user stories are a business analyst’s best friend whether your organization uses an Agile, Iterative/Spiral, or Waterfall software development approach.
What is business analysis about and why do we need more people involved in it?
Every project is a unique convergence of people, available technology, desired outcomes, and organizational culture. Ergo, those in authority should determine the appropriate SDM based on organizational as well as project factors and all options should be on the table for each project. How does the decision impact the one wearing the BA hat and how can you influence the decision?
Organizations initiate IT projects either to solve business problems or to seize business opportunities. Recognizing the difference is the challenge.
Strategic business analysis is exclusively a busienss function and should be executed by the business community. Tactical business analysis within a project can also be executed by the business community, but the IT group will do it in self-defense if they do not get good requirements from the SMEs. Operational business analysis is generally an IT function.
Business analysis is a skill similar to writing. That means that almost anyone can do it, but doing it well requires knowledge and practice.
Improving the efficiency of the organizaiton is one of the prime duties of business analysts. To be efficient at their job, they need time to do business analysis – and think..
User stories are becoming the preferred structure for expressing what business analysts call “Stakeholder Requirements”. Structuring them properly makes them even more powerful.