1 / 15

Beyond Requirements Dictator How Agile Helped a Business Analyst Discover Her Real Value

Beyond Requirements Dictator How Agile Helped a Business Analyst Discover Her Real Value. How Agile Helped A Business Analyst Discover Her Real Value by  Diane Zajac-Woodie  on 21 March 2014. Introduction. Diane Zajac-Woodie BA for 6 years,4 for them ”agile”. Outline.

mai
Download Presentation

Beyond Requirements Dictator How Agile Helped a Business Analyst Discover Her Real Value

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Beyond Requirements DictatorHow Agile Helped a Business Analyst Discover Her Real Value How Agile Helped A Business Analyst Discover Her Real Value by Diane Zajac-Woodie on 21 March 2014

  2. Introduction • Diane Zajac-Woodie • BA for 6 years,4 for them ”agile”

  3. Outline • Traditional BA’sjobs • The Obstacles • What stays the same • What changes • What skill even more valuable • Erasing role boundaries

  4. Traditional BA’sjobs • submitted in depth requirement plans • Createdetailed meeting minutes • precisely documented complexrequirements in meeting

  5. The Obstacles • Memberships • some team members were reluctant to embrace working in this type of environment. • Lack of information about agile • lack of information available for non-development roles on agile teams. • corporate culture • most large company encourages and rewards individual efforts

  6. The same and change • “What” a BA provides will stay the same • But “when” and “how” things are accomplished will change

  7. What stays the same • Still findrequirements • Still use BPM • BA still the communication hub • Still need meeting

  8. BPM • Business process models • Let new partner understand project easier and quickly • flexible – new information discovered and change • ***Share with stakeholder • ***hanging near the team space

  9. What changes • generate documentation to describe the pros and cons of each. → discuss with our product owners. • read a project initiation document → story map • executable test scenarios • Using Behavior-Driven Development (BDD), we spell out requirements in a ubiquitous language that literally becomes our automated tests. • Atthe front end of a traditional project → just-in-time

  10. Executable requirements

  11. Story map

  12. What skill even more valuable • Communication • Between business and developer • Among the teem • lean and share information • Curiosity • Work with PM to QA to developer • What is possible

  13. Erasing role boundaries • Small pieces of work • WIP(work-in-progress) limits • Everyone paring • Writing requirements • I know everything that I need • What can I learn from you

  14. WIP limits

  15. Conclusion • Erasing role boundaries made agile team more constant • Go agile made her discover her real value

More Related