1. Overcoming Geographical and Cultural Distribution:
Distributed Software Development
with Scrum and Social Coding
12.07.2011
Michael Lukas, Janos Koppany
© 2011 Intland Software 1

2. Agenda
• Distributed Software Development @Intland
• Live Demo
• V-Model and Waterfall
• Scrum & Kanban
• Social Coding
• Live Demo
• Questions and Answers
© 2011 Intland Software 2

3. Intland's History
• 2002 - CodeBeamer 1.0 – for early adopters
• 2003 – Collaboration extensions
• 2008 – codeBeamer, Jolt Award, Sun, 100.000 users
• 2011 – Cloud support (USDA)
ea mer
ALM
+
codeB
Collaboration
Integrations Prof.
SCMs, Services
Collaborative IDEs
Source Code Tool
Engineering Extensions
Features
© 2011I ntland Software 3

4. Intland’s Distributed Development
© 2011 Intland Software 4

5. What is “codeBeamer”?
• … an Application Lifecycle Management platform, supporting
development teams to manage their processes from requirements
to release.
• … increases productivity, provides full traceability, improves and
reduces costs by centralized management of processes, users and
projects.
• … offers collaboration and supports users to achieve an increase in
efficiency of up to 50%.
• … in practical use: a great collaboration solution!
© 2011 Intland Software 5

6. Process Support
Scrum, Kanban Waterfall, V-Process, Hybrid
© 2011 Intland Software 6

7. codeBeamer’s Operational Areas
• Project & Process Management • Distributed Software
• Requirements Management Development
• Change Management • Issue Tracking
• Knowledge Management • Ticketing System
• ITIL, SLA Management • Business Process
Monitoring
© 2011 Intland Software 7

8. V-Model
V-Model
© 2011 Intland Software 8

9. V-Model
Key Elements:
• Process Modules
• Validation and Tracebility
• Dependences between Modules
• Tasks that have to be executed
• Iteration Steps
© 2010 Intland Software 9

10. Waterfall or V-Process in codeBeamer
SW Requirements SW Validation cB Releases,
cB WIKI WIKI, Baselines
and Specification
documents
SW Design SW Integration
cB CMDB Spec.
+ cB Reporting, cB
Tracker Release
Component Component Integrated tools:
cB Projects Spec. Test HP QC,
Hudson,
build tools
Code
cB SCM
GIT, eGIT,
Gerrit, SVN
© 2011 Intland Software 10

11. Scrum & Kanban
Scrum & Kanban
© 2011 Intland Software 11

12. Scrum
Key Elements:
• User Stories
• Product Backlog
• Sprints
• Scrum Roles
(Scrum Master, Product Owner, Team)
© 2010 Intland Software 12

13. Scrum Wizard
© 2011 Intland Software 13

14. Scrum vs. V-Model
Scrum V-Model
Advantages Disadvantages Advantages Disadvantages
• Light weighted • No overview of the • Clear definition of • Less flexibility
process/ project whole process project phases • No clear resource
management • High communication • Complete overview disposition
• Short iteration effort (daily Scrum) of the whole process • Long iteration cycles
cycles, Sprints • Less architectural • Industries proven
• Easy to learn overview
© 2010 Intland Software 14

15. Combination of Scrum and V-Model in codeBeamer
• In codeBeamer, the artecfacts of both methods are combined - in
one project allowing to use the roles for Scrum and the defined
roles in V-Model.
User Stories,
Requirements, CB Product Backlog, Sprint Plan,
Tasks, Test SCM,
Builds, Project Overview Release Kanban,
V-Model In the release, all artifacts are Scrum
combined, allowing a complete
overview of Scrum working items
as well as V-Model items.
© 2010 Intland Software 15

16. Social Coding
Social Coding
© 2011 Intland Software 16

17. Centralized Work with Subversion, CVS, …
Central
repository
© 2011 Intland Software 17

18. DVCS Central Shared Repository
shared
repository
•Offline Work
•Merge
•Speed
A Developer B Developer C Developer
local local local
© 2011 Intland Software 18

19. DVCS Central Shared + Private Repository
repository shared
repository
•Offline Work
•Merge
•Speed
A Developer B Developer C Developer
local local local
© 2011 Intland Software 19

20. DVCS Fork/Pull-Request Workflow Example
Blessed
repository
© 2011 Intland Software 20

21. DVCS Fork/Pull-Request Workflow Example
Fork
creation
A Developer B Developer Blessed
public public repository
© 2011 Intland Software 21

22. DVCS Fork/Pull-Request Workflow Example
Creating a
local clone
A Developer B Developer Blessed
public public repository
A Developer B Developer Integration
local local Manager(s)
© 2011 Intland Software 22

23. DVCS Fork/Pull-Request Workflow Example
Starting a
Pull-request
A Developer B Developer Blessed
public public repository
Checkin changes Pull-request
A Developer B Developer Integration
local local Manager(s)
© 2011 Intland Software 23

24. DVCS Fork/Pull-Request Workflow Example
Merging changes in
blessed repositoriy
A Developer B Developer Blessed
public public repository
Merge
A Developer B Developer Integration
local local Manager(s)
© 2011 Intland Software 24

25. DVCS Fork/Pull-Request Workflow Example
Share changes
with the team
A Developer B Developer Blessed
public public repository
A Developer B Developer Integration
local local Manager
© 2011 Intland Software 25

26. GIT Workflow with Forks and Pull Request
Bless
Repository
Pull Request
Fork Integration
codeBeamer Server manager
Bob Developer
Remote Repository
Fetch Push
Bob Developer
Local Repository
© 2011 Intland Software 26

27. Live Demo
Live Demo
© 2011 Intland Software 27

28. Questions & Answers
Questions and Answers
© 2011 Intland Software 28

29. Thank you!
Thank you for your attention!
If you wish to have further information
please visit our homepage:
www.intland.com
www.javaforge.com
HgEclipse: http://www.javaforge.com/project/HGE
codeBeamer Eclipse Studio: http://www.javaforge.com/project/CBES
© 2010 Intland Software 29