12/11/2012 MOSP. MSE Summer 2012 Presenters: Ana Antunes João Ribeiro

Transcription

1 MOSP MSE Summer 2012 Presenters: Ana Antunes João Ribeiro 1

2 Agenda Team & Project Progress Scrum Monitoring Ana Antunes, João Ribeiro 2

3 Team&Project Progress Scrum Monitoring Scrum Team Filipe Norte Sofia Morais Sérgio Freire Pedro Feio David Cruz Ana Antunes João Ribeiro Development Team Client Liaison Scrum Master Client: Novabase Mentors Paulo Ferro Client & Product Owner Dave Root Marco Vieira Ipek Ozkaya Raul Barbosa Ana Antunes, João Ribeiro 3

4 Team&Project Progress Scrum Monitoring Problem Overview Ana Antunes, João Ribeiro 4

5 Team&Project Progress Scrum Monitoring epic Overview Approaches with Business Goals Automate project status communication Uniform project data collection Supports Central point of communication Standardizes information Tasks Risks Project Reports... Requires No continuous development support Disconnected from development artifacts COTS provide most intended functionality Project data collection Automatic reports epic Integrate COTS with Connecting Customize COTS to Novabase processes 5

6 Ana Antunes, João Ribeiro 6

7 Ana Antunes, João Ribeiro 7

8 Pedro Feio, Sofia Morais 8

9 Team&Project Progress Scrum Monitoring Progress How is the project going? Ana Antunes, João Ribeiro 9

10 Story Points Team&Project Progress Scrum Monitoring Progress: Must-have Releases 200 End of Semester 150 Progress Scope Change Release at End of Sprint Sprint Number Ana Antunes, João Ribeiro 10

11 Team&Project Progress Scrum Monitoring Strategies Product Owner unavailability Inefficient use of expertise Legacy system complexity Everyone contacts directly with the client Avoid intermediates Pair programming Coach and inexperienced member together Solve complex problems with discussion Ana Antunes, João Ribeiro 11

12 Team&Project Progress Scrum Monitoring Scrum How is Scrum Working? Ana Antunes, João Ribeiro 12

13 Team&Project Progress Scrum Monitoring Scrum Sprint 2 Weeks Responsabilities Scrum Master Product owner Client Liason Development Team Quality Manager Configuration Manager Risk Manager Chief Architect Ana Antunes, João Ribeiro 13

14 Team&Project Progress Scrum Monitoring Scrum Unable to finish all stories within a sprint Technical expertise is not uniform Individual goals are not completely aligned Democracy is time consuming Helps predict team velocity Deliver value each sprint Knowledge sharing and communication 14

15 Team&Project Progress Scrum Monitoring Monitoring How is our effort distributed? Ana Antunes, João Ribeiro 15

16 Team&Project Progress Scrum Monitoring Monitoring Task Distribution Overall Design 10% 5% Coding 23% 32% Product Quality Assurance Product Re-Work Configuration Management Requirements Management Risk Management 3% 3% 8% 3% 13% Ana Antunes, João Ribeiro Project Plan, Monitoring and Control Process Definition & Improvement 16

17 Team&Project Progress Scrum Monitoring Plan Planning, Monitoring and Process Improvement Sprint Planning 1% 12% 11% 5% 36% Backlog Refinement Sprint Retrospective Sprint Review Daily Scrum Collect and Report Metrics 9% Mentoring Team Survey & Nokia Test 11% 3% 9% 3% Ana Antunes, João Ribeiro Others Process Definition 17

18 Plan Time distribution 100% Team&Project Progress Scrum Design Coding Monitoring 80% 60% 40% 20% 0% Sprint 1 Sprint 2 Sprint 3 Ana Antunes, João Ribeiro Product Quality Assurance Product Re-Work Configuration Management Requirements Management Risk Management Project Plan, Monitoring and Control Process Definition & Improvement 18

19 Not reported Not reported Team&Project Progress Scrum Monitoring Monitoring Quality Time Spent Verifying (hours) Nr of Defects Found Ana Antunes, João Ribeiro 19

20 Team&Project Progress Scrum Strategies Monitoring Inefficient meetings Radically redefining processes Discussion meetings prepared in advance Topics to discuss and order Facilitator responsible for eliciting decisions Eliminate distractions in meetings Avoid disruptive process changes Ana Antunes, João Ribeiro 20

21 Q&A Thank you! Ana Antunes, João Ribeiro 21

22 22

23 TFS DataStore TFS contains a relational Warehouse and a multidimensional data cube (i.e. OLAP cube) TFS structure does not assume any particular measures or data structure TFS allows to add, remove or edit work item types TFS analysis features allow to develop customized reports Ana Antunes, João Ribeiro Ref: 23

24 Ana Antunes, João Ribeiro 24

25 Ana Antunes, João Ribeiro 25

26 Ana Antunes, João Ribeiro 26

27 Ana Antunes, João Ribeiro 27

28 Ana Antunes, João Ribeiro 28

29 Does TFS support Novabase required reports? 1. Novabase already has defined a set of Processes that should be used. 2. Novabase Process Framework recomend a set a project reports that should be delivered 3. Some teams already use TFS 4. Novabase required metrics are already defined Ana Antunes, João Ribeiro 29

30 Business Goals (BG) BG 1: Ease access to projects information Real and updated information available BG 2: Decrease manual work Automatically generate project information such as: Project progress status Development tasks progress Pedro Feio, Sofia Morais 30

31 Project context 10 Novabase pilot teams starting on September Gain positive feedback Encourage Novabase s Administrators to make future investments in the base system Ana Antunes, João Ribeiro 31

32 Project Progress - Expected Backlog Items Must have Should have Nice to have Bonus Backlog Items effort estimation 54% 43% 2% 1% Backlog Items Expected Completion May 2012 % Completion (worst velocity estimated) % Completion (average velocity estimated) 57% 81% Ana Antunes, João Ribeiro 32

33 Story Points Velocity Control Average velocity Story points closed in sprint Sprint Ana Antunes, João Ribeiro 33

34 Project Progress: work completed Process template (XML) TFS System SAP DB SQL SAP Reads Configuration SAP System SQL TFS http VS http Check New Project Step Flow Configuration (XML) http http Create New TFS Project Step Reads Configuration http Connecting http... Create Main Process Flow Step n Reads Configuration Site Template (XML)... Writes Log Project Server http Create PS project Step SharePoint Applications David Cruz, Sérgio Freire Log File (txt) Create New Project <Scheduled task> 34

35 Project Progress: work completed Process template (XML) TFS System SAP DB SQL SAP Reads Configuration SAP System SQL TFS http VS http Check New Project Step Flow Configuration (XML) http http Create New TFS Project Step Reads Configuration http Connecting http... Create Main Process Flow Step n Reads Configuration Site Template (XML)... Writes Log Project Server http Create PS project Step SharePoint Applications David Cruz, Sérgio Freire Log File (txt) Create New Project <Scheduled task> 35

36 Project - Client Novabase IT Solutions Company 2000 employees Internal and external development Business areas Aerospace & Transportation Energy & Utilities Financial Services Government & Healthcare Manufacturing & Services Telecoms & Media Ana Antunes. João Ribeiro 36

37 Project Progress: Release Plan Sprint Planned Release features Actual Release features Sprint 1 Create New Project Module UPDATE Releases Sprint 2 TFS Connecting Integration Customized process template Sprint 3 Project Setup Customized process template Create New Project Module Office documents generation Sprint 4 Sprint 5 Sync Tool Build configuration Office document generation Provide Offline Environment TFS Connecting Integration Build configuration Project Setup Sync Tool Project Server Integration Sprint 6 Project Server Integration Provide Offline Environment Ana Antunes, João Ribeiro 37

38 Risks Category Technology Processes Technology Title Total votes Total voters Team members are inexperienced in domain technology; team may underestimate tasks due to unknowns in technology and effort needed to help others We aren't collecting metrics on processes; We may not be able to improve inefficient processes Synch tool and PS architecture design aren't finished; We may not be able to implement the product according with the highlevel design and need to redesign Product owner wants to be involved on implementation details; He may require changes (on code, detailed design,... ) during Product Owner sprints Requirements Most product functionalities is not being validated with users; Final product may not fit the purpose of the pilot teams Ana Antunes, João Ribeiro 38