improving It s what we do. TM

Transcription

1 improving It s what we do. TM

2 Agile Team Roles Business Analyst & QA Analyst Susan Fojtasek Tonya Guadiz

3 Agenda Development Processes Business Analyst Quality Assurance Analyst What does this mean to me?

4 Traditional Development Lifecycle

5 Agile Individuals & Interactions processes & tools Working software comprehensive documentation

6 Burn down Scrum Business Case Financing Scope & Approach Contracts Initial Release Plan Assemble Team Daily Scrum < 15 minutes Product Owner establishes vision and prioritizes Product Backlog Sprint Planning 1 day Acceptance Defined Team commits Tasks created Sprint 1 to 4 weeks Sprint Review 1/2 day Sprint Retrospective 1/2 day Team (BA, QA, Dev, etc.) creates and estimates Sprint Backlog (tasks) Releasable Increment velocity Burn up

7 BA QA Burn down Scrum Business Case Financing Scope & Approach Contracts Initial Release Plan Assemble Team Daily Scrum < 15 minutes Product Owner establishes vision and prioritizes Product Backlog Sprint Planning 1 day Acceptance Defined Team commits Tasks created Sprint 1 to 4 weeks Sprint Review 1/2 day Sprint Retrospective 1/2 day Team (BA, QA, Dev, etc.) creates and estimates Sprint Backlog (tasks) Releasable Increment velocity Burn up

8 Scrum Teams Scrum teams are optimally 7 +/- 2 people Scrum only defines 3 roles Product Owner ScrumMaster Development Team ScrumMaster BA Sponsor Team QA Stakeholders Product Owner

9 The Team Cross-functional group (PM, Architects, programmers, BAs, testers, UI designers, DBAs, etc) that have committed to accomplishing the goals of the sprint

10 Agenda Development Process Business Analyst Quality Assurance Analyst What does this mean to me?

11 Business Analyst Business Analyst vs. Systems Analyst Business IT

12 What Does Agile Mean to You? Misconception: I m no longer a valued team member Requirements don t need to be captured Product owner is responsible for writing requirements now I only have to worry about the high level user stories, the details will be figured out by the developers Don t throw away everything you ve been taught about being a BA

13 Responsibilities Objective: Define the scope of a project Identify what should be built Investigate & Analyze Communicate Document

14 Agile Responsibilities Facilitation Breadth, then Depth Don t get so wrapped up in process and documentation

15 Characteristics Inquisitive Detail-oriented Thorough Big picture focus Be flexible

16 Challenges Team doesn t pay attention to requirements Transition to new mindset: Don t have to know all the details up front You are no longer the single source of information, rather you are the facilitator Be involved with your team

17 Agenda Development Processes Business Analyst Quality Assurance Analyst What does this mean to me?

18 Quality Assurance Analyst or Tester Quality Assurance vs. Testing Quality Assurance Set of preventative activities Adherence to standards and processes Testing Investigation Focus on product output

19 Team member who: Agile Tester Collaborates well with technical and business people Not a quality police officer Drives agile testing Agile testing is more explicitly a service role Serves the business expert and the programmers

20 Misconceptions: What Does Agile Mean to You? Excuse to skip test documentation Toss aside all existing test skills Does mean an attitude and mindset adjustment

21 Objective: Ensure quality software Responsibilities

22 Agile Responsibilities Quality is a whole team concept Create tests collaboratively Translator & idea generator Be part of the requirements analysis process Acceptance tests are developed before software Test early and often - Provide continuous feedback

23 Traditional Characteristics Domain knowledge about the system under test Level of technical competency Attention to detail Results oriented Agile Novelty-seeking personality Flexibility Communication and collaboration

24 Challenges Maintaining a high level of regression coverage Anticipating the unknowns Adjusting your mindset from traditional to agile Breaking through others perception of the tester role

25 Agenda Scrum & Team Roles Overview Business Analyst Quality Assurance Analyst What does this mean to me?

26 What do you see?

27 Heresy Can the BA and Tester roles be combined? Common skills and characteristics Commonality of deliverables Should BA and Tester roles be combined?

28 Ponder Title = Role

29 What Does it Mean to Lead? Attitude Focus on the goal delivery Avoiding it s not my job mentality Walk the talk

30 What happens when.

31 Additional Resources IIBA International Institute of Business Analysts Dallas and Ft Worth Chapters ALN Agile Leadership Network Dallas and Ft Worth Chapters

32 Relevant Training Agile Acceptance Testing March Improving's Addison Location Becoming an Effective Product Owner February Improving's Addison Location Scrum.org Professional Scrum Master Certification March Improving's Addison Location May Code Magazine s Houston Location Agile Scrum Immersion March Improving's Addison Location April Code Magazine s Houston Location

33 Questions?

34 THANK YOU! Susan Fojtasek Tonya Guadiz