The Eclipse Project's Development Process is not the only way a project can be run and still meet the requirements of the overall Eclipse Development Process. This talks describes how concepts from Scrum and XP can be applied successfully to delivering eclipse projects on the release train, or ahead of it.

3. 8300 Unit Tests

4. Originally Failed over 90 % of Xpath 2.0 Test Suite

5. 3 Part-Time Community Developers not Paid by Members

7. Passes 8300 Unit Tests

8. Test Results, FindBugs Trends, and Duplicate Code Stats available on Hudson.

9. Project run using Techniques in this Talk.

10. Adopters – Apache Xerces-J for XSD 1.1 Assertion support.

12. Plan is produced 3 months into the Development.

13. Not all features done have a corresponding bugzilla

15. Too many bugs that LOOK like they are being fixed but are not.

17. Failure to have Unit Tests or Functional Tests

18. Developer/User Documentation is treated as an after thought

20. Communication

21. The Agile Manifesto–a statement of values Mountain Goat Software and www.agilemanifesto.org Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working software over Contract negotiation Customer collaboration over

22. Project Planning

24. Scrum In Pictures Image available at www.mountaingoatsoftware.com/scrum

28. Prioritized by the Product Owner/Community.

29. The work that is PLANNED to be done during an iteration.

33. Allows for clear communication to the community

34. Shows what is ACTUALLY being worked on

35. Keeps Developer/Committer backlog manageable

36. Review at the end of each iteration and before the next iteration begins. Re-evaluate the backlog.

37. Technical Practices

41. Write Unit Tests.

43. Communicate Project Health

46. Work is not completed until all tests pass on both your machine and the build machine.

47. Fix Failing Tests as soon as they happen. There is no such thing as a random failure.

48. Do not be afraid to Refactor. Tests can allow you to refactor ugly code to Clean maintanable code.

50. Clean Code – Robert Martin

52. Scrum Alliance

53. Mountain Goat Software

54. Eclipse Development Process