Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseCon 2009/BoF/Agile
< EclipseCon 2009
Revision as of 23:24, 8 March 2009 by Ketanpadegaonkar.gmail.com (Talk | contribs) (added page for discussing points about BoF)
- agile applied to agile: you need to be agile with agile
- try out small changes to your process
- put in measures to detect failures early
crutique about things that slow you down
- lack of out-of-the-box CI support
- legacy code that gets in the way of doing design using doing TDD and mock-objects
on being 'agile with agile':
- if agile does not work for you then you need to change it
- there's no process, but there's still order in the percieved chaos
- the process is not the king, people are
- many forms of Agile, even RUP can be agile if done right
- working through the problems, not around it (1 day code freeze to stabilize things is not a solution, repetitive builds with tests that run every check in is)
- less fat in the UI -- better APIs in the core, that can be tested