Mozilla - SoftVision Team

1. To improve

1.1. Few people on IRC (time-zone problem)

1.2. Communication on Automation side

1.3. Mozilla specific IRC primer - would help

1.4. Guidelines about what to do and ehen (pioritization of task)

1.5. Attend more meetings

1.6. Repeatable tasks

1.7. Ramp-up documents & test specs on Automation (i.e. tests from done examples, tasks should be be more specific)

1.8. Features changing overnight - OWNER to update the spec, as a solution - watching the wiki page

1.9. WinXP tests take to much time - compatibility issues

1.10. Involvment

1.11. Litmus tests should be updated by the owner

1.12. SV to take ownership on inactive things: AI - Mozilla will provide access.

1.13. New TestCase management System in work by Mozilla

1.14. Improve rating of Fennec on Android market

1.15. FYI: www.arewepretty.com

1.16. Have on the current QA Wiki pages - the official info - to be gathered on ScrumPads

1.17. For features that don't have UseCases - SV team should take initiative and create UC

1.18. More involvement in the Automation comunity - P2PU - the basics of Selenium - focused more on WebQA - David to improve Automation area

1.19. AI: Once a month Automation Test Day

1.20. Info of who's in charge of different areas - S: follow the bugs, see who's in charge; care about what's your projects about, observe through time the people involvment - and when updating the page in Litmus provide this list as well

1.21. What means to own a feature: a set of responsibilities to be defined: start interact with the guys who construted Panorama

1.22. Mozilla's growth poses new challenges

1.23. increase initiative

1.24. Don't ask for permition - just do it and ask for feedback

1.25. Interact with a lot of mozilians to communicate

1.26. Communicate closer with developers - their feedback is valuable

1.27. Follow-trough - investigation through a bug should be followed up all the way

1.28. Using ScrumPads more efficient - to improve communication

1.29. More responsibility for the team

1.30. Have initiative when starting new tasks - not just wait for juan's/Tony's emails

1.31. Identify things important/non-important to test on

1.32. SCRUM PADS - very important to be used efifeciently

2. Good Stuff

2.1. Good working transparent communication

2.2. Initiative

2.3. AI: ramp-up inside the team

2.4. AI: File all issues

2.5. Feature ownership

2.6. Involved in Test Day

2.7. Spirit & Energy of the team - Passion

2.8. Acces to information & changes

2.9. Team growth

2.10. Scrum Pads - good idea

2.11. Flexibility

2.12. Respected ETAs

2.13. Ideas are taken into account

2.14. Availability to answering Questions

2.15. Trust increase

2.16. Updates on Wiki's

2.17. Responsiveness

2.18. Attention & focus on indication from Mozilla

2.19. Grown to understand the project, business

2.20. Thouroughness - details on information provided

2.21. Perseverence