|
|
|
|
 |
| |
|
|
| |
|
|
| |
Monday, June 7 – Tuesday, June 8, 2010 |
|
| |
The importance of business analysis and the business analyst’s role in project and product success is growing rapidly. Increasingly, organizations large and small are formalizing business analysis as a discipline, seeking people with business analysis skills, and aligning around the International Institute of Business Analysis (IIBA®) Business Analysis Body of Knowledge (BABOK®) standard. Today, many business analysts are challenged to adapt traditional requirements practices to the new demands of agile development.
Whether you come into the work of business analysis from the business or technical side of the organization or whether you work on traditional or agile teams, all competent analysts need grounding in the disciplines encompassed in business analysis.
New for 2010, the two-day Business Analysis Workshop on Monday and Tuesday focuses on the knowledge and skills that will make your business analysis work successful. Led in a highly interactive, engaging style and guided by experts with extensive experience and a passion for business analysis, this workshop provides you with practical takeaways you can use immediately. After the workshop, continue your learning at the conference on Wednesday and Thursday by choosing from concurrent sessions tailored to your business analysis and requirements needs.
In this two-day workshop you will:
| |
• Learn what knowledge and skills are embodied in the discipline of business analysis |
| |
• Learn pragmatic techniques for understanding your users and their needs |
| |
• Understand how to navigate the IIBA® BABOK® (The Business Analysis Body of Knowledge) |
| |
• Explore how to adapt traditional business analysis practices in the agile environment |
| |
• Discover how business analysis and testing can interact effectively on both traditional and agile projects |
| |
|
|
|
| |
The two-day Business Analysis Workshop is appropriate for anyone involved in business analysis: business analysts, systems analysts, requirements analysts, business managers, project managers, developers, product owners, test analysts, user experience analysts, ScrumMasters, and internal consultants. |
|
|
GO TO: Monday Tuesday
|
|
|
|
| Business analysis is a core process and role for defining and delivering software products in all organizations. What knowledge and competencies comprise the discipline of business analysis? Who in the organization is best suited to take on the role of business analyst? How can organizations develop top analysts who help teams deliver great products? Mary Gorman presents a broad range of business analysis topics, including requirements development, requirements management, process modeling, business analysis certification, and common business analysis modeling tools and techniques. Begin this two-day Business Analysis Workshop by participating in an interactive survey of these foundational skills and knowledge within the broad practice of business analysis. With your active participation, produce a visualization of the skills of the consciously—and unconsciously—competent analyst. |
 |
| Learn more about Mary Gorman |
|
|
| Networking Break • 9:50 a.m. |
|
|
|
|
|
| Understanding the needs and wants of diverse groups of users is critical to a product’s success. In this fast-paced session, Jeff Patton leads you through the basics of user identification and analysis. Learn to identify distinct types of users and how to gain a deeper understanding with research approaches such as interviews, focus groups, and surveys. After doing a little research on your own, you’ll practice creating a lightweight user persona—a concrete example of a member of your user community. Learn to leverage personas to identify specific product implications based on each user persona’s needs. These techniques give you a deeper understanding of your users and help you and the development team leverage that understanding to identify and validate more accurate and useful software requirements. |
 |
| Learn more about Jeff Patton |
|
|
|
|
|
|
| Some say business analysts and testers are just different sides of the same coin: They’re both concerned with making sure the development team delivers what the customer wants. Business analysts have a vested interest in how a feature is tested and may even perform testing activities themselves. Lisa Crispin defines the different types of testing done in typical software projects, including who does which tests, whether they’re manual or automated, and when they should be run. She examines ways that business analysts (BAs) can help make sure the right testing tasks are planned and executed. Explore how BAs collaborate with testers and other development team members to involve customers, ensure the right tests are specified, and see that the right code gets written. The session includes a brief overview of test automation and how BAs can help ensure it brings value to the customers and the product. |
 |
| Learn more about Lisa Crispin |
|
|
| Networking Break • 1:50 p.m. |
|
|
|
|
|
| The International Institute of Business Analysis (IIBA®) Business Analysis Body of Knowledge (BABOK®) is a globally recognized standard for the practice of business analysis. It describes the generally accepted business analysis knowledge areas, tasks, and techniques. Whether you are new to the discipline of business analysis, a seasoned business analysis professional, or someone studying for for the Certified Business Analysis Professional™ (CBAP®) designation, you need to be able to skillfully navigate through the BABOK®. Mary Gorman, a four-year veteran of the IIBA® Body of Knowledge Committee, guides you along a variety of pathways through the BABOK® using the analysis techniques described in the BABOK® itself. Learn how to visualize the underlying foundation of the BABOK®, trace the foundational elements throughout the BABOK®, and apply analysis modeling techniques to navigate the BABOK®. Join this journey to help you analyze your own competencies against the BABOK® framework. |
|
| Learn more about Mary Gorman |
|
|
|
|
|
|
| Wrap up your first day in the Business Analysis Workshop with a panel discussion, facilitated by Lee Copeland, on specific business analysis development and management practices—for both traditional and agile development environments. With a panel of experienced business analysis professionals, explore how BA work is both art and science, identify ways to adapt your toolkit of practices to different projects and environments, and increase your value to yourself, your team, and your organization. Bring questions, issues, and concerns you may have about fitting your business analysis experiences into today’s world. The panel members share their experiences in both traditional and agile teams, examine the benefits and challenges for analysis, explore challenges in transitioning practices to different project types, and discuss why they are passionate about business analysis. Engage with the panel and other participants to explore what you need to do to grow and flourish in your business analysis practices. |
 |
Learn more about Ellen Gottesdiener
Learn more about Jeff Patton
Learn more about Lisa Crispin
Learn more about Mary Gorman |
|
|
| |
|
|
|
|
| Ellen Gottesdiener, EBG Consulting |
|
|
| Many agile analysis practices are significantly different from those used on a traditional project. Ellen Gottesdiener introduces the changes in analysis timing, elaboration, documentation, and validation on an agile project through the EBG Consulting Agile Requirements Roadmap. She shares the value of sketching out the big view of the product to establish a common focus and marshal organizational resources, how to preview requirements for a release, and techniques to select high-priority options for the iteration at hand. You’ll discover how to orient yourself to the three views of an agile project: product, release, and iteration. See and experience how requirements are elaborated across these three views and practice essential analysis techniques for slicing requirements for incremental delivery. Participate in contrasting the practices of a “traditional” business analyst role with those needed on an agile team. |
|
| Learn more about Ellen Gottesdiener |
|
|
| Networking Break • 9:50 a.m. |
|
|
|
|
|
| In agile projects, user stories have emerged as the most common way to describe user needs and drive the planning process for iterative and incremental delivery of the software. With ten years of experience working with user stories, Jeff Patton leads you through a deeper understanding of user stories and how they compare to other analysis and requirements communication approaches. Working in small teams, you’ll create a user story map—an arrangement of stories that helps you understand the whole product as a set of related user stories. Learn about the lifecycle of a typical user story from identification, decomposition, and elaboration using acceptance criteria all the way to verifying finished stories during each agile iteration or Scrum sprint. Return to work with new insights into how user stories can help you and your project—whether or not you work in an agile development lifecycle. |
|
| Learn more about Jeff Patton |
|
|
|
|
|
|
| How do we know when a software feature is ready to release? It can be complicated to make the call. Who actually decides? How do they know that they have enough information to decide correctly? Although we perform testing to gather information about the quality of the product, testing often gets squeezed at the end of the project. Lisa Crispin explains how BAs can help their business users and the entire software team define what “done” means and how to get the information you need to know you are ready to release. Learn how to use examples, user scenarios, and test cases to augment and clarify business requirements. Discover new strategies to ensure there is time for the right amount of testing. Explore user acceptance testing (UAT) practices and other ways to obtain timely customer feedback and approval. Find out how all these activities fit nicely into the short iterations of agile projects. |
|
| Learn more about Lisa Crispin |
|
|
| Networking Break • 1:50 p.m. |
|
|
|
|
|
| On agile projects, requirements unfold within the context of the rhythm of agile planning: product, release, and iteration. Collaborative workshops provide an effective venue for agile—and non-agile—teams to work together transparently to make complex decisions about what to build, and when. Ellen Gottesdiener explains how to calibrate your requirements based on the appropriate workshop: product roadmapping workshop (to explore and allocate the big-view of requirements and map out a strategy for the entire product), release planning workshop (to focus on a smaller time horizon to get a pre-view of requirements for the next release), and iteration planning workshop (to explore and plan for a small, concise set of requirements for the immediate iteration, the now-view). Learn about these useful workshops, the skills you need to plan and facilitate them, and how workshops enable agile teams to make smart choices to create a healthy project community sharing focus, values, and trust. |
|
| Learn more about Ellen Gottesdiener |
|
|
|
|
|
|
| Conclude your Business Analysis Workshop experience with a retrospective to reflect on the key learning, skill transfer challenges, and strategies for implementing new skills and practices when you return to your team and organization. Together with your colleagues and the presenters, you’ll recap the first day’s visualization of the analyst’s skills and update it with new insights from the participants. Leave with innovative ideas and newly gained skills to help you put your personal development needs into action to become a more consciously competent business analyst! |
|
| Learn more about Ellen Gottesdiener |
|
|
| |
|
|
Back to Top
|
|
|
 |
|
|
|
|
