MSE Studio: Automated Test Framework

1. MSE Studio: Automated Test Framework Middle of Semester Presentation 2008-10-17 Presenter: António Pedro Alvim The Mappers team 1

2. Agenda Project background Team organization Project roadmap Reflections Questions 2

3. Agenda Project background Team organization Project roadmap Reflections Questions 3

4. Project background • Q/A Department • Internal/external projects quality assurance • ATF will be one integrated tool which facilitates the testing process by taking into consideration the Q/A unit best practices and enables to work in a more efficient way. 4

5. Project background • Client view: • Lack of traceability between requirements and test • Best practices to be implemented • Lack of automation • Our understanding: • Reduced test time • Time consuming methodology • Manual and repetitive work process • Varied tools and artifacts • Varied testing approaches 5

6. Major Challenges • Client negotiation • Scope • Expectations management • Definition of threshold of success: • Information system? • Automation of test cases generation from requirements? • Integration with other tools currently used? 6

7. Agenda Project background Team organization Project roadmap Reflections Questions 7

8. Team • Mentors: Mário Rela, David Root, Marco Vieira 8

9. Processes • Meetings: • Internal (weekly)status | brainstorming |reflection • Mentors (weekly) • Client - Project Manager • Phone, e-mail (weekly), personal • Agenda and minute tracking for all meetings • Action item tracking • Tools: • Mediawiki, SVN, Bugzilla 9

10. Processes • Planning: • WBS and time allocation: • Top down definition • Bottom up time estimation • Weekly data gathering of all team members • On going measure of expected/actual budget • re-adapt wrong estimations • Earned Value Management • Risk analysis: • Identification and plan on mitigation 10

11. Agenda Project background Team organization Project roadmap Reflections Questions 11

12. Roadmap Logistical setup Team organization Documentation analysis Fall Semester planning WBS Schedule Outlines for fall deliverables Contextual Interviews Wrapping up contextual design Consolidation Client Walkthroughs Drafts for fall deliverables On going reflections Meetings and processes Schedule reviewing Get client feedback Scope negotiation Risk Workshop Finish Studio Fall Deliverables Requirements specification We’ve done We’re doing We’re going to do 12

13. Requirements • Techniques for elicitation used: • Client Interviews • Needs for the application • Contextual Design • 2 rounds of interviews with 20% of end-users • Analyzing techniques for specification 13

14. Schedule • Section of planning detail: • Note: not effort, but calendar and sequence indication 14

15. 0/100% Rule Note: time excluding bootcamp. 15

16. Next Steps • Choose appropriate software development process • Start requirements specification • Risk assessment workshop • After better defined requirements 16

17. Agenda Project background Team organization Project roadmap Reflections Questions 17

18. Reflections • Team work • Entire team involved on major decisions • Trade-off: budget vs. information sharing • Meeting time keeper helps to keep focus • Information record • Rationale behind decisions • Client presented solution upfront • Understand problem before solution • Currently mitigated with requirements elicitation 18

19. Reflections • Plan ahead is important • Proactive: Risk and Impact discovery • Future work (calendar deadline identification) • Estimations should consider technique learning curve • Need to improve our EVM usage • Contextual design • Multi dimensional analysis of the problem • Unveils hidden information • Useful to understand client’s culture • Expensive 19

20. Agenda Project background Team organization Project roadmap Reflections Questions 20

21. Questions for mentors • EVM – to improve project control: • Break the management tasks across the different weeks? • Meetings • Support • Processes Management • Configuration Management • … 21

22. Questions for mentors • Best timing for scope discussion with client? • Our approach: • 1st: Present our Vision • Result from Contextual Design Consolidation • Show new solution identified by our vision • 2nd: Present UED Diagram • Estimates for focus areas • Teams’ studio budget • Let the costumer decide what to build 22

23. Questions We want to listen to your questions! 23

24. Roles - Detailed 24

25. Contextual Design – Why? • Need to understand work process and Q/A Context • Share information across team • Identify users involved in the work process • end users: Tester / Team Leader / Project Manager • Artifact/tool usage in projects • End-user involvement • 20% interview coverage • identification of relevant work issues: • Flow, sequence, culture, artifacts • New technique for team

26. Software Development Lifecycle • Still have to define what final application will include: • Information System • Automated Prototype • Management dashboard • This will influence the choice of an appropriate lifecycle

27. Risk assessment 27

28. Planning – Process 28

29. Planning – Estimation • Estimation Methods: • Expert Judger • Based on prior experience • Tailored Wideband Delphi • Estimation period: • For recurrent weekly tasks • Total task time • To do: define process for planning reschedule 29

30. Planning - Strategies Available Effort BCW Scheduled Planned Effort Actual Effort BCW Performed • Measures of Plan Success 30