Microsoft PowerPoint - BA Masterclass Session 10 - BA in Agile 2018.pptx

21600-10 2018 Business Analysis in Agile ASPE Business Analysis Masterclass - Session 10 877-800-5221.

[Audio] In Agile, we adopt a more flexible approach to managing requirements, which is more temporal, interactive, and just-in-time. The traditional software requirements specifications, design specifications, and similar documents no longer exist, and neither does the implied obligation to deliver everything on a predetermined schedule and with fixed resources..

[Audio] The role of a business analyst in an Agile environment involves becoming a value manager, ensuring the value of each delivered sprint is realized. This requires being a system thinker, considering factors such as alignment with strategies, other initiatives, enterprise architectures, releases, and more..

[Audio] The role of the business analyst in Agile is to ensure that the value of each delivered sprint is realized by aligning with strategies, other initiatives, enterprise architectures, releases, and thinking systemically..

[Audio] The Agile Manifesto emphasizes collaboration between stakeholders, prioritizing working software, and continuous improvement..

[Audio] The Agile Manifesto highlights the significance of customer collaboration over contract negotiation. Rather than negotiating a predetermined set of requirements beforehand, we focus on establishing a connection with our customers and adapting to their evolving needs throughout the development process..

[Audio] As collaborating within a smaller team and with fewer stakeholders on a continuous basis, early and often, using simple tools during conversations allows us to work towards a shared definition of "done", acknowledging that changes will occur and are acceptable, thinking customer-first, this approach enables us to focus on business value, prioritizing individuals and interactions over processes and tools, and responding to change over following a plan. By doing so, we can deliver working software, rather than comprehensive documentation, and engage in customer collaboration over contract negotiation..

[Audio] The code is developed daily through pair programming, test-driven development, and continuous integration, which maintains the stability and maintainability of the codebase throughout the development process. Daily stand-ups are held to ensure everyone is aligned and aware of their tasks and progress. Sprints usually last between two to four weeks, allowing for focused work on specific goals. After each sprint, the next sprint's goals are defined, ensuring continuous improvement and adaptation to changing requirements..

[Audio] In this context, we are examining the vision, programs, projects, and portfolios. Creating a roadmap and release planning are crucial steps. Here, we define what we aim to achieve and how we will accomplish it. Subsequently, we employ a Sprint Zero to establish the foundation for our Agile endeavor. Ultimately, we gaze towards the subsequent sprint, consistently considering the larger perspective..

[Audio] In an Agile approach, time is estimated flexibly, whereas in a Waterfall approach, time is fixed and constrained. This flexibility enables greater adaptability and responsiveness to changing requirements..

[Audio] In this Agile environment, the business analyst plays a crucial role in ensuring that the needs of stakeholders are met. This requires competencies such as communication, facilitation, and negotiation skills. As an engagement model, the business analyst works closely with the development team to understand their requirements and ensure that they are aligned with the overall strategy..

[Audio] Business analysts can utilize the knowledge areas outlined in the BABOK guide to operate effectively in an Agile setting. The key areas encompass planning, requirements management, requirements analysis, solution evaluation, and implementation. By grasping these knowledge areas, business analysts can guarantee that their efforts align with the organization's goals and objectives..

[Audio] Business analysts play multiple roles in an Agile environment. They can act as stakeholders' proxies or work directly with sponsors or product owners. This flexibility allows them to adapt to changing priorities and ensure that the value of each delivered sprint is realized. As a value manager, their primary goal is to maximize the value delivered to stakeholders. In doing so, they may distribute some business analysis activities to other team members, allowing the team to collaborate effectively..

[Audio] The business analyst in an Agile environment must have specific competencies. They should be adaptable, trustworthy, knowledgeable about business, and able to improve through adaptive approaches. Conceptual and systems thinking are also essential skills. Moreover, collaboration with the team and good verbal communication skills are vital for successful interactions..

[Audio] As a business analyst in an Agile environment, I need to keep the big picture in mind by applying conceptual and systems thinking. This requires ensuring alignment to strategy, roadmaps, and architectures, while providing domain translation between business and technology. Defining and communicating acceptance criteria is also crucial, as well as maintaining a value focus as a Value Manager. Furthermore, I need to support the Product Owner role, uncover missing requirements, drive change, and look ahead to future developments..

[Audio] The techniques of business analysis do not undergo significant changes in the agile environment. However, their application and usage do change. Artifacts like personas, data models, use cases, story maps, and business rules remain employed, but are maintained as lightweight as possible..

[Audio] In this context, personas are fictional characters or archetypes of users who may interact with the product. They help us better understand users from their perspective. Although they may not be real people, they should be described as such, including characteristics like name, personality, background, skills, behaviors, attitudes, motivations, and values received. By creating these personas, we can determine which ones will receive the most benefit from our product..

[Audio] As a stakeholder, I need to do something so that I can achieve a specific benefit. This fundamental concept defines user stories. By verifying and ensuring certain details and acceptance criteria, we can populate the product backlog with high-priority user stories that meet the needs of our stakeholders..

[Audio] As a stakeholder, I need to describe a requirement in a specific format so that I can capture the essence of what I'm trying to achieve. A user story is a way to do this, breaking down an epic into smaller tasks with their own acceptance criteria, which define when each task is completed. This helps me understand what I'm building and why. By elaborating on these user stories, I can create a clear picture of what I'm trying to accomplish..

[Audio] In determining prioritization techniques, we consider criteria for ranking, such as the Purpose Alignment Model and the Kano Model. We prioritize lower items that are not yet fully understood, as well as top items that are more valuable and more granular. This approach ensures that our backlog is aligned with the project's goals and objectives..

[Audio] In this Agile environment, we look at ways to document requirements effectively. We can use lightweight documentation techniques, such as functional decomposition, partial data modeling, UML behavior diagrams, organization charts, context diagrams, and swim lane diagrams. These methods help us capture the essential information needed to understand the requirements without overwhelming ourselves with unnecessary details. By keeping our documentation concise and focused, we ensure that everyone involved in the project has a clear understanding of what's required..

[Audio] Any user who interacts with a product or service can be described as a persona by considering their characteristics, needs, goals, behaviors, and motivations. This approach enables us to gain a deeper understanding of our users and develop a more effective and user-centered design..

[Audio] Grooming the backlog involves several activities, including requirements discovery, sprint planning, and sprint conversations. These activities help ensure that the backlog is well-groomed, prioritized, and ready for development. By splitting user stories into smaller, more manageable chunks, we can better understand the requirements and deliver them efficiently. This process enables us to refine our understanding of the product and adapt to changing priorities..

[Audio] As user stories play a crucial role in the Agile process, they define stakeholder requirements using a simple statement on a card. The card points to a needed conversation, which is then elaborated upon for confirmation. These user stories populate the product backlog, and high-ranked ones are extracted for sprint backlogs. It is essential that these user stories are completed within a sprint, either by being fully developed or by being split into smaller tasks. This ensures a healthy and evolving backlog..

[Audio] As we move forward, it's essential to leverage business requirements and scope definition to build our backlog. This involves using personas to gain a deeper understanding of our users and their needs. We will elicit user stories through common techniques, uncover any business and technology constraints, and break down larger user stories into smaller, more manageable pieces. By doing so, we will ensure that our backlog is well-defined and ready for development..

[Audio] In this stage, we are examining the Sprint Planning process. It is crucial to consider the broader perspective as we progress. We must contemplate the overall vision, roadmap, and architecture of our project. This necessitates being mindful of any concealed assumptions that may arise during these discussions. Furthermore, we should facilitate the division of user stories into manageable portions, ensuring that all parties are synchronized and moving in the same direction..

[Audio] As a business analyst, I would help developers and testers clarify their questions about the requirements during conversations. I would probe to uncover any additional requirements that may not be immediately apparent. Additionally, I would assist in defining the acceptance criteria for the requirements, ensuring that everyone involved understands what it means to meet the requirement..

[Audio] As a theater customer, I expect to find a seat with its associated ticket price so that I can make a decision on whether the ticket price is reasonable. To determine if the ticket price is reasonable, I would consider factors such as the location of the seat, the type of event being held, and any additional amenities provided. I do not assume that all seats have the same ticket price, as prices may vary depending on these factors. While making my decision, I would also consider any specific information about the seat, such as its proximity to the stage or the quality of the view..

[Audio] As a member, I need to enroll in the system so that I can access my membership information. Verify that the enrollment process is successful, and ensure that the authentication ID and password are generated correctly..

[Audio] The code is developed daily through pair programming, test-driven development, and continuous integration, which keeps the codebase healthy and maintainable throughout the project lifecycle. Daily stand-ups are held to ensure everyone is aligned and aware of their tasks and progress. Sprints usually last between two to four weeks, allowing for flexibility and adaptability in response to changing requirements. After each sprint, the next one is planned, ensuring continuity and momentum in the development process..

[Audio] Resources are available to support your learning journey. Visit our website for more information..

[Audio] In this example, we observe a lightweight context diagram, which visually represents the relationships between various elements in the system. This diagram enables us to comprehend the context in which our requirements are being developed. By analyzing these relationships, we can identify the primary actors, their objectives, and the events that trigger actions. This information is vital in defining our user stories and acceptance criteria. As business analysts, it is imperative that we collaborate closely with the development team to guarantee that our requirements accurately reflect the needs of the users. By doing so, we can deliver high-quality solutions that satisfy the needs of our customers..

[Audio] As we explore creating user stories that capture the requirements of our product backlog, we will examine the essential elements of a good user story, including its title, description, acceptance criteria, and estimated effort. By completing this worksheet, one gains a better understanding of how to craft effective user stories that meet the needs of stakeholders and the development team..

[Audio] As we conclude, I would like to express gratitude for taking the time to review these resources, which include the Business Analysis Body of Knowledge V3, the Agile Extension to the BABOK Guide V1, and Agile Software Requirements by Dean Leffingwell. These references offer valuable insights and guidelines for business analysts operating in Agile settings. We appreciate your focus and hope you found this presentation enlightening..