traditional vs agile roles

17
Traditional Roles Traditional Roles vs. vs. Agile Roles Agile Roles

Upload: sumit-mahajan

Post on 10-May-2015

243 views

Category:

Technology


1 download

DESCRIPTION

Compares various agile and traditional roles

TRANSCRIPT

Page 1: Traditional vs Agile Roles

Traditional Roles Traditional Roles vs.vs.

Agile Roles Agile Roles

Page 2: Traditional vs Agile Roles

Compare the Traditional Roles vs. Agile Roles 1. Sponsor vs. Product Owner

2. Project Manager vs. ScrumMaster 3. BA vs. Agile BA 4. Tester vs. Agile Tester 5. Developer vs. Agile Developer

AgendaAgenda

2

Page 3: Traditional vs Agile Roles

3

Agile Team StructureAgile Team Structure

Page 4: Traditional vs Agile Roles

Projects have one sponsor, usually higher in the organization Projects have one sponsor, usually higher in the organization chart, funds the project but is not involved in the details.chart, funds the project but is not involved in the details.

Multiple business stakeholders are involved to provide input Multiple business stakeholders are involved to provide input and requirements.and requirements.

No one decision maker.No one decision maker. Engaged at the start of the project and then towards the end Engaged at the start of the project and then towards the end

during testing.during testing. Usually receive weekly status reports from PM on how the Usually receive weekly status reports from PM on how the

project is doing and if any issues need their attention. project is doing and if any issues need their attention.

4

Traditional SponsorTraditional Sponsor

Page 5: Traditional vs Agile Roles

Person in charge of the product backlog i.e. requirements.Person in charge of the product backlog i.e. requirements. Prioritizes the backlog stories based on business value.Prioritizes the backlog stories based on business value. Most likely from the business. Most likely from the business. Accepts or rejects work completed.Accepts or rejects work completed. Knowledgeable, Empowered and Engaged.Knowledgeable, Empowered and Engaged. Only one who can add or remove stories from the backlog.Only one who can add or remove stories from the backlog. Owns final success or failure of project.Owns final success or failure of project.

Product OwnerProduct Owner

5

Page 6: Traditional vs Agile Roles

Manages the project through developing detailed project plans Manages the project through developing detailed project plans upfront at the task level.upfront at the task level.

Heavy upfront planning, may engage key SMEs for estimates or Heavy upfront planning, may engage key SMEs for estimates or provide ones themselves.provide ones themselves.

Manages tasks, holds weekly status meetings. Manages tasks, holds weekly status meetings. Takes care of addressing any major team issues. Takes care of addressing any major team issues. Maybe managing several projects at a time.Maybe managing several projects at a time. Accountable for project success and failure.Accountable for project success and failure. May use Command and Control to tell team what to work on May use Command and Control to tell team what to work on

next and by when to get it done. next and by when to get it done.

6

Traditional Project ManagerTraditional Project Manager

Page 7: Traditional vs Agile Roles

7

Is a ‘Leader’ of the team who creates a culture of high collaboration, team Is a ‘Leader’ of the team who creates a culture of high collaboration, team empowerment, and high visibility and accountability. Owns the ‘Process’.empowerment, and high visibility and accountability. Owns the ‘Process’.

Engages the product owner and business SMEs upfront to develop the Engages the product owner and business SMEs upfront to develop the product backlog. Holds product owner accountable for owning the product backlog. Holds product owner accountable for owning the backlog.backlog.

Is knowledgeable on Agile Requirements Gathering methods and Story Is knowledgeable on Agile Requirements Gathering methods and Story identification, breakdown and estimation techniques. identification, breakdown and estimation techniques.

Very light use of project management tools. Spends most of their time Very light use of project management tools. Spends most of their time with the team and removing impediments. with the team and removing impediments.

Heavy initial release planning then continuously engages team to update Heavy initial release planning then continuously engages team to update the plan each sprint. the plan each sprint.

Holds daily 15 minutes standup meeting with all team members involved Holds daily 15 minutes standup meeting with all team members involved including the product owner. including the product owner.

The ScrumMasterThe ScrumMaster

Page 8: Traditional vs Agile Roles

May manage only one large project or a couple of smaller May manage only one large project or a couple of smaller projects at one time. projects at one time.

Is not accountable for project success and failure.Is not accountable for project success and failure. Uses a Servant Leader style for leading the team. This results in Uses a Servant Leader style for leading the team. This results in

self organizing, empowered and accountable teams. self organizing, empowered and accountable teams. Empowers the committed team members from Business and IT Empowers the committed team members from Business and IT

to make decisions. Does not make business or technical to make decisions. Does not make business or technical decisions on behalf of them. decisions on behalf of them.

Understands and has experience with iterative delivery of Understands and has experience with iterative delivery of projects with focus on Business value. projects with focus on Business value.

Measures and reports progress frequently using easy to Measures and reports progress frequently using easy to understand burn down charts. understand burn down charts.

May hold Certified ScrumMaster certification. May hold Certified ScrumMaster certification.

8

The ScrumMaster…cont’dThe ScrumMaster…cont’d

Page 9: Traditional vs Agile Roles

Analyze business need to help identify business problems and Analyze business need to help identify business problems and proposed solutions.proposed solutions.

Acts as liaison between the business and IT.Acts as liaison between the business and IT. Will meet with various stakeholders at the beginning of a project Will meet with various stakeholders at the beginning of a project

to elicit requirements in detail. to elicit requirements in detail. May use Use Case specifications or other type of documentation May use Use Case specifications or other type of documentation

to capture all requirements.to capture all requirements. May require business to sign off on requirements upfront on a May require business to sign off on requirements upfront on a

project.project. Probably trained on upfront detailed requirements gathering as Probably trained on upfront detailed requirements gathering as

opposed to iterative requirements elaboration. opposed to iterative requirements elaboration. Collaborates on the project heavily upfront then again during Collaborates on the project heavily upfront then again during

testing to validate requirements were met and possibly during testing to validate requirements were met and possibly during development to clarify ambiguity. development to clarify ambiguity.

9

Traditional Business AnalystTraditional Business Analyst

Page 10: Traditional vs Agile Roles

The BA/SA is the owner of requirements documentation and elicitationThe BA/SA is the owner of requirements documentation and elicitation. . They are a master of They are a master of Agile Requirements Gathering Agile Requirements Gathering and know how to and know how to

break down stories into small valuable chunks.break down stories into small valuable chunks. Understand how to capture Understand how to capture storiesstories, , user test casesuser test cases, , business rules, business rules,

process diagrams, UI prototypes process diagrams, UI prototypes and other artifacts. and other artifacts. An Agile BA An Agile BA engages the business engages the business SMEs and product owner with the SMEs and product owner with the

team instead of acting as a liaison/middleman to the business. team instead of acting as a liaison/middleman to the business. They They manage the backlog manage the backlog of stories by adding, removing, updating of stories by adding, removing, updating

stories there (after Product Owner approval) and keeping it up to date. stories there (after Product Owner approval) and keeping it up to date. They will They will schedule and facilitate requirements elicitationschedule and facilitate requirements elicitation sessions and sessions and

make sure the right SMEs are invited. make sure the right SMEs are invited.

The Agile BAThe Agile BA

10

Page 11: Traditional vs Agile Roles

They will make sure that all They will make sure that all scope changes scope changes have been appropriately have been appropriately capturedcaptured and and documenteddocumented on the backlog. on the backlog.

During the iteration, the BA works on making sure the During the iteration, the BA works on making sure the requirements and acceptance criteria are understood requirements and acceptance criteria are understood by by developers for all stories. developers for all stories.

They are very They are very effective Facilitators effective Facilitators and know how to bring the and know how to bring the team to their goals from any sessionteam to their goals from any session. .

They They work ahead with the product owner work ahead with the product owner to define stories and to define stories and test cases for the next iteration.test cases for the next iteration.

The work closely with testers (IT or business) to The work closely with testers (IT or business) to track testing track testing progressprogress..

Use Use light weight, easy to readlight weight, easy to read, and , and accessibleaccessible documentation. documentation. They make sure the right individuals are using the artifacts They make sure the right individuals are using the artifacts produced. produced.

11

The Agile BA…cont’dThe Agile BA…cont’d

Page 12: Traditional vs Agile Roles

The testing group is usually engaged towards the end of the project.The testing group is usually engaged towards the end of the project. This group may require upfront complete documentation on This group may require upfront complete documentation on

requirements in order for them to develop test cases.requirements in order for them to develop test cases. Work closely with the BAs to clarify missing requirements.Work closely with the BAs to clarify missing requirements. Use of issue tracking tools to log bugs and get them assigned to Use of issue tracking tools to log bugs and get them assigned to

developers in addition to tracking their status. developers in addition to tracking their status. May use heavy weight testing tools to document and manage all May use heavy weight testing tools to document and manage all

test cases and track progress on each one. test cases and track progress on each one. May use automated testing and load testing tools. May use automated testing and load testing tools. Traditionally they have final say on if the software is ready to be Traditionally they have final say on if the software is ready to be

tested by the customer or move into production.tested by the customer or move into production.

12

Traditional TesterTraditional Tester

Page 13: Traditional vs Agile Roles

Engaged earlyEngaged early during the project, part of the core team. Could be a during the project, part of the core team. Could be a business user tester or a QA test engineer or have both.business user tester or a QA test engineer or have both.

Uses Uses automated testing automated testing whenever feasible.whenever feasible. QA test engineers work ahead of the next iteration to QA test engineers work ahead of the next iteration to help setup test help setup test

datadata, , help identify additional test cases help identify additional test cases needed.needed. During each iteration QA testers During each iteration QA testers work closely with developers work closely with developers to to

know when stories are ready for their initial testing.know when stories are ready for their initial testing. They They perform testing, log and track issuesperform testing, log and track issues and provide feedback to and provide feedback to

developers. developers. They keep track of where each story is at in terms of testing and how They keep track of where each story is at in terms of testing and how

close it is to ‘Done’ and may send out daily emails with progress.close it is to ‘Done’ and may send out daily emails with progress. They They collaborate with the team daily collaborate with the team daily during the 15 minute standup. during the 15 minute standup.

The Agile TesterThe Agile Tester

13

Page 14: Traditional vs Agile Roles

Engaged on the project after planning has been completed and the Engaged on the project after planning has been completed and the project is ready for development.project is ready for development.

Is expected to read the documentation on requirements to Is expected to read the documentation on requirements to understand what the software needs to do. Goes through BA for understand what the software needs to do. Goes through BA for additional questions.additional questions.

Works of the upfront designs produced by the architect.Works of the upfront designs produced by the architect. Does not usually have access or care about test cases. Driven more Does not usually have access or care about test cases. Driven more

by requirements documented by BA.by requirements documented by BA. May or may not be aware and follow company coding standards May or may not be aware and follow company coding standards

and architecture best practices.and architecture best practices. Mostly works independently. May get assigned tasks from PM with Mostly works independently. May get assigned tasks from PM with

specific due dates.specific due dates. Mostly works vertically focusing on ‘Front end’ ‘Business logic’ ‘Data Mostly works vertically focusing on ‘Front end’ ‘Business logic’ ‘Data

logic’ areas instead of horizontally focusing on each business story. logic’ areas instead of horizontally focusing on each business story.

14

Traditional DeveloperTraditional Developer

Page 15: Traditional vs Agile Roles

Engaged from the beginning of the project. Helps story sizing, Engaged from the beginning of the project. Helps story sizing, dependency identification and initial release planning.dependency identification and initial release planning.

During each iteration, the developer is working on understanding During each iteration, the developer is working on understanding requirements and using Test Driven Development as a method of requirements and using Test Driven Development as a method of implementing them.implementing them.

They create automated unit tests for each test cases and may use They create automated unit tests for each test cases and may use mock data when real data is not readily available or to reduce mock data when real data is not readily available or to reduce dependencies. dependencies.

They frequently check in their code and aim for continuous They frequently check in their code and aim for continuous integration. integration.

They must focus on one story at a time and work They must focus on one story at a time and work HorizontallyHorizontally instead of the typical instead of the typical VerticalVertical way we worked in waterfall. way we worked in waterfall.

The Agile DeveloperThe Agile Developer

15

Page 16: Traditional vs Agile Roles

They follow the company’s coding standards and recommended They follow the company’s coding standards and recommended designs. designs.

They work closely with the user on testing each story as it passes They work closely with the user on testing each story as it passes a few test cases or become ‘Done’.a few test cases or become ‘Done’.

They raise issues and impediments daily and only work on the They raise issues and impediments daily and only work on the most valuable stories and tasks. most valuable stories and tasks.

They are engaged, flexible, collaborative, quality driven and They are engaged, flexible, collaborative, quality driven and focused on the iteration goal.focused on the iteration goal.

16

The Agile Developer…cont’dThe Agile Developer…cont’d

Page 17: Traditional vs Agile Roles

Thank You!Thank You!

Prepared by: Sumit MahajanPrepared by: Sumit Mahajan

17