About Me / Alfresco. Alfresco Software, Open Source Enterprise Content Management

Transcription

1 Jean Barmash, Alfresco Software January 15, 2008 About Me / Alfresco Director, Technical Services Blog Alfresco Software, Open Source Enterprise Content Management Document Management Web Content Management Enterprise 2.0 / Social Computing Platform 1

2 Agenda Program Introduction Iteration 1 Spring Program Iteration 2 Summer Program Iteration 3 Fall Program Conclusions Training Boot Camp Top Financial Services Company 10 Week Program 1 Week Traditional Training 6-Week-long Project, different each time Students straight out of college 3 Times / Year Spring - 22 People Summer 22 People Fall 16 People 2

3 Goals of the Program Enterprise Coding Practices Complete project lifecycle Teamwork Integrated Final Project QA Practices Final Presentation to Senior Management Everybody must talk Demos Iteration 1 - Spring Program 22 Students Project - Operations Dashboard Easy technology Working with existing team Goal move to production Code Review Process JUnit Tests 3

4 Basic Process for All Projects Agile-Like Teams of 3-5 Split up based on Technology components Clearly defined responsibilities Each Team has a Team Lead Daily Team Meetings Special Team for Operations Everybody in the same training room Rough Schedule Week 1 Kickoff, Design Week 2 Initial Implementation Week 3 Final Component Implementation Week 4 Integration / QA Week 5 Presentation / Practice Week 6 Final Presentation 4

5 The Room Spring Program - Conclusions Outcome Pretty Good Major problems with integration Some QA, but could be better Code Reviews Documentation Integration Tests System Tests 5

6 Lessons Learned Need more show and tells Need better prioritization Wanted team to have flip charts of priorities Need Spikes Checklists for how to approach a task Focus on Integration from beginning Iteration 2 - Summer Program Complicated research-oriented project Challenging Technical Problem Emerging Technologies Lots of integrations between components Rambunctious Class 6

7 Challenges Hard Technologies Emphasis on learning technologies No Build Process, almost until end Performance Testing very hard Let Quality Lapse Not as important No Code Reviews Integration not until late Status Dashboard 7

8 Summer Lessons Learned Need clearer prioritization Dashboard was very useful Need to renew emphasis on Quality Need to prioritize build process Introduce Scrum? Iteration 3 -Fall Program Document Generation Component To be shared across other teams Production-quality New Technology, but not too difficult Smaller Class - 16 Most Diverse, both in terms of roles and geographies 8

9 Fall Program Decided to use Scrum Luxury of decreeing it Challenge how do you teach and use scrum at the same time? Scrum Elements Well Defined Sprints Task Board Impediments List Burn Down Chart Daily meetings (from before) Spikes Team Meetings QA Push QA Leads Show and Tells External Internal Prioritization Example 9

10 Team Scrum Experience Well Defined Sprints- good Task Board good, after changes Burn Down Chart- bad No Estimation Daily meetings (had all along) Spikes QA Push QA Leads Show and Tells External Internal 10

11 Task Board s Not Started In Progress Complete Access Template Statement Class Taskboard Console Operations Problems What s a Task? Requirements Management Tool Issue Tracking Task Boards Dashboard Dashboard overload had too many categories Burn down Charts Team Meetings 11

12 QA Dashboard Example Test Plan JUnit Tests Build Runs Tests Code Coverage 75% CheckStyle Style Stubbing / Faking Integration Testing Tests Modeled in Mercury Scrum Lessons Learned Summary Task Board For Each Team Dashboard Too Much Burn Down Chart Daily Scrum Meeting 30 mins minimum QA Dashboard QA Leads 12

13 Social Task Board Fall Results Iteration 3 - Best Project of the Three Most Work Accomplished Emphasis on Quality and Process Reasons We got better this was my third time Students had good attitude, smaller team Scrum 13

14 Questions / Suggestions? 14