Presentacin de PowerPoint

1
(No Transcript)
2
Agenda

• Presenters profile
• Freeride motivation
• Continuous drawbacks
• Controlled integration
• Mixing controlled and continuous
• Conclusions

3
Presenters profile

• Pablo Santos Luaces Codice Software
• Engineer Software, MHP, ERP
• Plastic SCM
• Support high level SCM features
• Implement new capabilities

4
Freeride

• Agiles spirit
• High skilled staff
• Freedom to perform changes
• Refactor
• Better code
• Boost productivity
• Create a real team

5
Team
6
Freeride

• Change whatever needs to be changed
• Enforce collective code ownership
• Have fun -gt global business requires getting the
  best out of talented people

7
Rigid / fully controlled processes

• Better predictability
• Better documented
• More industrial
• Less staff dependency

• Less implication, people dont feel the product
• Groups of people, not teams
• Innovation just achieved by a few

8
The role of SCM in agile

• Create the environment to achieve the goals
• Not every tool fits
• Is not just a commodity, SCM is a cornerstone to
  build upon
• Help enforcing the change process
• Agile / Freeride doesnt mean
• Chaos
• Unnecessary reworking
• Everyone having the same skills

9
Continuous drawbacks

• Non-stop integration
• mainline instability!
• No testsuite is complete -gt continuous can create
  chaos

10
Continuous drawbacks

• Unnecessary bug spreading
• Everyone needs to integrate
• bad for newcomers
• bad for big teams

11
Continuous drawbacks

• Code outside the version control for too long
• Fridays commit nightmare!

12
Controlled integration

• Tests are key, like in continuous
• An integrator takes full responsibility
• Not everyone has to deal with merging
• Task oriented development -gt introduce full
  parallel development

13
Task oriented cycle
14
Task oriented cycle

• Everything is a task (good for agile, good for
  CMMi)
• Task independency (branching patterns)
• Code not so long out of the SCM
• No merge rush
• Integration is a planned task
• Better isolation
• Version control serves developers

15
Task oriented

• Most commits are just checkpoints
• Isolation avoids dependencies and mainline
  corruption

16
One task one line
17
Best of both worlds

• Running tests on developers workstations
• It takes time
• GUI testing is blocking
• Results are not published
• Release building in the continuous world is
  supported by tools

18
Integration alternatives

• Integrators merges
• Integrators run tests
• Integrators pack, label

19
Integration alternatives

• Developers merge (small teams) and run tests
• Integrators pack, label
• Avoid mini-big-bangs
• Shorten release building times

20
Integration alternatives

• Developers merge (small teams) and run tests
• Keeps mainline clean

21
Conclusions

• Get the best of both worlds
• Avoid confusion (continuous doesnt mean
  non-stop)
• SCM can benefit agility
• SCM can enable parallel development

22
www.codicesoftware.com