Designing An Agile Community Program: Funambol Code Sniper v. 2
0 likes879 views
The document describes Funambol Code Sniper v2, an agile community program for developing open source software. Version 2 addresses limitations of Version 1 by having community members write user stories, prioritize backlogs, and earn points for developing and testing stories that can be exchanged for money or goods. This encourages community involvement and active roles beyond just development. Challenges include cultural barriers, educating on agile practices, and balancing roles. Advantages include earlier user involvement, emergent requirements, and increased incentives for ongoing contributions and maintenance. Open questions remain around estimating stories and defining "Done".
Designing An Agile Community Program: Funambol Code Sniper v. 2
- 1. Designing An Agile Community Program Funambol Code Sniper v. 2 Stefano Maffulli, Community Manager Agile Day Bologna Nov 20 th 2009
- 2. Open Source and Agile Main assumption: customer = community
- 3. Funambol Code Sniper v 1 Current setup Funambol maintains a list of 'wanted' software
- 4. Community members pick one and write a proposal
- 5. The proposal is discussed with the Funambol engineers and approved
- 6. Code Sniper developer writes a full specifications and submits them for approval to Funambol
- 8. Once code is working according to specs the grant is released
- 9. End
- 10. Sniper Developer Code Sniper v1 process Community & Funambol Eng
- 11. Limits Too much 'solo' work
- 12. Possible conflicts Two people or groups want to develop the same project Risk of abandonment decreased incentive to maintain the software after version alpha is released Not agile
- 13. Funambol Code Sniper v. 2 Funambol keeps a list of desired software
- 14. Customers (community) write user stories, create backlog
- 15. Developers (community) evaluate user stories and take them to develop
- 16. For each story written and completed, community members earn Sniper Points Write a User Story = 1 point
- 17. Develop a User Story = X points (according to evaluation)
- 18. Test a User Story = x/2 points Sniper Points can be exchanged with money or goods
- 19. Code Sniper Process v. 2
- 20. Challenges Overcome the cultural barrier Educate on what a user story is or how to write an effective one Provide effective and easy to use tools Few free-as-in-freedom software suitable for Agile mgmt Balance the mixed roles of owner, developer and customer with very small teams Some projects may not be well suited for an Agile Open Source method (example: those few users)
- 21. Advantages The community takes an active role involve users, not just developers, at early stage
- 22. involve users for testing and approving stories Requirements emerge as a shared effort of the community (the Product Owner)
- 23. The project grows step by step, each step is releasable as per the definition of user story Developers can pick up small chunks of functionality (it better meets people's time constraints)
- 24. Increased incentives to contribute after initial release as long as more user stories are added there is incentive to contribute and maintain the code
- 25. Open questions How to estimate User Stories? Hours? Weeks? Story Points? Do they make sense? How to define 'Done'? The community should define DONE Ideas: Changes Log and Design Document updated
- 26. Unit tests implemented and passed
- 27. Acceptance tests defined and passed no new bugs on the user story, no regression bugs Releasable (installable and working in real life conditions)
- 28. Documentation, upgrade impact, backward compatibility, performance impact
- 29. Further discussion Join Funambol Discussion Forum