Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (10)
Semelhante a Rally at AT&T - Sigal Pasternak - Agile Israel 2013
Semelhante a Rally at AT&T - Sigal Pasternak - Agile Israel 2013 (20)
Mais de AgileSparks
Mais de AgileSparks (20)
Último
Último (20)
Rally at AT&T - Sigal Pasternak - Agile Israel 2013
- 1. Rally Implementation @ AT&T Israel Sigal Pasternak © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
- 2. AT&T Rally Implementation sizing © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.2 47 Scrum teams 500 People 4 LOBs 31 Discovery teams
- 3. Every day, 500 employees in AT&T Tel-Aviv, log into Rally to gain the visibility and collaboration needed to transform our business requirements into delivered projectsreleases 3
- 4. Importance of tool Implementation when adopting Agile • Practices alignment across teams • Implement terms, concepts and language • Standard view • “Safety net” for managers Visibility improvement • Transferring mindset from tasks tracking to backlog/business value tracking • Quick win Visibility © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.4
- 5. © 2010 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained herein are the property of their respective owners. SEP 2011 Started the Agile implementation journey in 2 LOBs (~16 Scrum teams) Agreed on light evaluation process Identify the need for “safety net” Visibility on release level and few products backlog RTC VS. Rally Piloted Rally and RTC in parallel for two weeks OCT 2011 Executed short training In two weeks, 200 users were in production NOV 2011 Rally full blown implementation, 2 more LOBs (446 users) Rally implementation Evolution DEC 2011
- 6. Task Task Task AT&T Development Life Cycle AGILE Development Product Development Testing Demo 3 Weeks Sprints Daily Meetings Continuous Integration Working Software Demo Retrospective Product elaborates Items into prioritized Epics2 5 Discovery team elaborates Epics into prioritized ‘Ready’ User Stories 3 Items Gathering1 (Prioritized) Product Backlog User Story User Story Epic User Story Epic Item 4 Sprint Backlog Team selects how much to commit to do by Sprint’s end Sprint Planning 5 Scrum TeamDiscovery Team
- 7. Iteration planning board © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.7 BugsTasks Progress Remaining days Plan Est Owner Iteration scope vs. Planned velocity
- 8. Iteration planning board © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.8
- 9. Iteration planning board © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.9
- 10. Sprint planning based on velocity & capacity 10
- 11. Ideal status © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.11
- 12. Iteration cumulative flow © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.12 What can we learn? 1. One day is remaining to the sprint 2. Small amount of Accepted 3. High WIP (Work In Progress) – the team is working on all stories in parallel (are QA and Dev really working together?) Allows you to view the states of work in the iteration to analyze the trend in lead time for delivery of working code
- 13. Rally implementation challenges 1. Scrum oriented (weak support in Kanban) 2. No dynamic list, no dependencies between fields 3. No triggers 4. Can’t define holidays in calendar (badly affect Burndown) 5. Can’t have default values 6. Weak bulk update 7. No permissions 8. Release Burndown doesn’t count (planned vs.) velocity © 2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.13
- 14. © 2010 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained herein are the property of their respective owners. 14
Notas do Editor
- View of stories and defects ready to be scheduled, and any work items scheduled in the next three iterationsUse this boardas part of discovery processto prepare for and carry out iteration planningduring the Planning sessionThe board provides multiple features that allow you to:Drag Stories into the correct iterationView up to three upcoming iterations in addition to the backlog columnView the velocity for each iteration at the top of each columnSearch the backlog column for work itemsHover over the ID field to view the description of the card Drag a card vertically to change its priorityAdd new work items (stories, tasks)Create, update and delete tasksView and update discussionsView and update associated defects
- Allows you to view the states of work in the iteration to analyze the trend in lead time for delivery of working code Use this chart toForecast and track progress: indicate the progress of your work as it moves to completionManage scope: it is easy to see when scope is added or decreasedIdentify bottlenecks: determine if there are trends that indicate bottlenecks. For example, a large section of completed may indicate a PO roadblockOptional action itemsLimit WIP (Work In Progress) to max 2 open stories per developer ‘Push’ PO to Accept (if there are Completed stories)