Metodologías Agiles en E///

Transcription

1 Metodologías Agiles en E/// La organización y las personas Antonio Montero (ScM & Agile Coach)

2 Agile originally conceived as a set of software development values and principles. E/// worked Based on Waterfall method: One big project A sequential process Req. Anal. Design BT&UT FT S. Test Now in Agile: Flexible Many small projects Highly collaborative Best for those who want continuous improvements Involves customers A process in which requirements are expected to evolve and change Scrum Development Deliverable Deliverable Public Ericsson AB Page 2

3 Public Ericsson AB Page 3

4 Success keys to implement Agile methodology in an organization Commitment and support "real" by the direction / management, providing human and technical resources E/// Dif. Organizat. - Dif. Results Implementation throughout the business value chain E/// Important - PL Proper training of employees in the new way of working Public Ericsson AB Page 4

5 Scrum & Kanban Public Ericsson AB Page 5

6 SCRUM TEAM Public Ericsson AB Page 6 XFT team

7 PRODUCT OWNER Manages Product Backlog Identify and prioritize The voice of the customer - E///???? What & why but not How Provides acceptance criteria (DoD) and Accept (ornot) the sprint result. Stakeholders XFT team Public Ericsson AB Page 7

8 SCRUM MASTER Scrum master is neither a project manager, nor a line manager Shields the team and educates others outside the team about how the team is working Facilitator, improves Team productivity Removes impediments - E///: ScM - Line Managers ScM - 50% Designers 100% ScM How many teams - One ScM??? Public Ericsson AB Page 8

9 CROSS FUNCTIONAL TEAM XFT: includes everyone required to build the product (All disciplines) E///: SM - Des - Tester - ST Seven plus or minus two members E/// 5-8 Commits to delivering the Sprint Backlog Responsible for product quality Self-organized & stable - E///: yes in sprint Not in time Public Ericsson AB Page 9

10 BURNDOWN CHART User Story Public Ericsson AB Page 10 VELOCITY

11 Sprints 2 to 4 week consecutive time period where the team builds the Product Backlog items they committed to during Sprint Planning - E///: 2 3 weeks No changes are allowed during the Sprint No change to team composition No change to committed work (the User Stories in the Sprint Backlog) - E///: Yes usually The end of the Sprint is fixed Public Ericsson AB Page 11 11

12 Daily Scrum The Daily Scrum is often a Stand-Up meeting and is timeboxed to 15 minutes Three questions: What did you complete since the last daily Scrum? What impediments got on your way? What are you going to complete before the next daily Scrum? Not a status meeting to the ScrumMaster After the meeting, only for interested people. If someone has something important to share. Public Ericsson AB Page 12

13 TRACKING in the DAILY Public Ericsson AB Page 13

14 Public Ericsson AB Page 14 BURN-DOWN CHART

15 Does agile fit with members in different places? TOOLS Ericsson Communication Client (ECC) IBM Sametime Microsoft Lync Skype TeamSpeak Mumble OpenMeetings Taskboard Public Ericsson AB Page 15

16 Scrum process overview Artifacts and Ceremonies Public Ericsson AB Page 16

17 THE PRODUCT BACKLOG Feature A Old Prod. Feature B Feature C Feature D Public Ericsson AB Page 17

18 Participants: Product Owner, Scrum Master & Development Team Goal: Prepare the Product Backlog for the Sprint planning meeting. This usually includes adding new stories and epics, extracting stories from existing epics, and estimating effort for existing stories. E/// - It is the team who estimate the effort Scrum Backlog Grooming Public Ericsson AB Page 18 18

19 Sprint Planning meeting Participants: Product Owner, Scrum Master & Development Team Goal: Select Product Backlog items Create Sprint Backlog Achieve Sprint Goal commitment E/// - It is the team who is committed to deliver x functionality in this sprint Public Ericsson AB Page 19 19

20 Sprint Review Meeting Participants: Product Owner, Scrum Master & Development Team and any other interested. Goal: Review backlog items delivered in Sprint Check if Sprint Goal is achieved, Get common understanding of product State Sprint Review Sprint Review Sprint - 3 w. Sprint - 3 w. Sprint - 3 w. Public Ericsson AB Page 20 Sprint Demo

21 Sprint demo Why? Show architecture and infrastructure works How? 1-2 hours Performed by Team Must show product potentially ready for production Audience is Product Owner and customers/users E/// - Called, as well, Technical Presentation To: PLM, Customer Units, Product line (Our stakeholders) Public Ericsson AB Page 21

22 Sprint Retrospective PO Product Owner SM Development Team Scrum Master Public Ericsson AB Page 22

23 Public Ericsson AB Page 23

24 KANBAN - Used in maintenance - System Verification teams Public Ericsson AB Page 24

25 Public Ericsson AB Page 25

26 Success keys to implement Agile methodology in an organization Commitment and support "real" by the direction / management, providing human and technical resources Implementation throughout the business value chain Proper training of employees in the new way of working Public Ericsson AB Page 26

27 Public Ericsson AB Page 27

28