Verteilte Software Entwicklung 2011von klassischen Modellen bis Scrum und Social Coding                       27. Juni 201...
Agenda• About Intland and codeBeamer• Live Demo• V-Model and Waterfall• Scrum & Kanban• Social Coding• Live Demo• Question...
Intlands History• 2002 - CodeBeamer 1.0 – for early adopters• 2003 – Collaboration extensions• 2008 – codeBeamer, Jolt Awa...
Intland’s Distributed Development                        © 2011 Intland Software   4
What is codeBeamer• codeBeamer is an Application Lifecycle Management platform that  helps development teams to manage the...
codeBeamer’s Operational Areas• Project, Process                    • Distributed Software  Management                    ...
V-Model          V-Model           © 2011 Intland Software   7
Process Support        Scrum, Kanban                             Waterfall, V-Process, Hybrid                        © 201...
V-ModelKey elements:• Process modules• Validation and Tracebility• Dependences between modules• Task that have to be execu...
Waterfall or V-Process in codeBeamer                                   SW Rquirements                             SW Valid...
Scrum & Kanban            Scrum & Kanban                 © 2011 Intland Software   11
ScrumKey elements:• User stories• Product Backlog• Sprints• Scrum Roles  (Scrum Master, Product Owner, Team)              ...
Scrum Wizard               © 2011 Intland Software   13
Scrum vs. V-Model  Scrum                                                   V-ModellAdvantages             Disadvantages   ...
Combination of Scrum and V-Model in codeBeamer• In codeBeamer the artecfacts of both methods are combined in  one project ...
Social Coding                Social Coding                    © 2011 Intland Software   16
Centralized Work with Subversion, CVS, …                     Central                     repository                       ...
DVCS Central Shared Repository                          shared                          repository                        ...
DVCS Central Shared + Private Repository          repository                 shared                                     re...
DVCS Fork/Pull-Request Workflow Example                                                Blessed                            ...
DVCS Fork/Pull-Request Workflow Example                                                                 Fork              ...
DVCS Fork/Pull-Request Workflow Example                                                                  Creating a       ...
DVCS Fork/Pull-Request Workflow Example                                                                 Starting a        ...
DVCS Fork/Pull-Request Workflow Example                                                     Merging changes in            ...
DVCS Fork/Pull-Request Workflow Example                                                          Share changes            ...
GIT Workflow with Forks and Pull Request                    Bless                    Repository                           ...
Live Demo            Live Demo               © 2011 Intland Software   27
Questions & Answers                  Questions and Answers                        © 2011 Intland Software   28
Thank you for your attention             Thank you for your attention                 If you need further information     ...
Upcoming SlideShare
Loading in …5
×

Verteilte SoftwareEntwicklung 2011 - von klassischen Modellen bis Scrum und Social Coding

1,227 views

Published on

Präsentation auf der Seacon 2011 in Hamburg.

Neueste Trends in der verteilten Software Entwicklung: Collaboration Tools für EntwicklungsTeams, Einsatz von DVCS

Published in: Technology
1 Comment
1 Like
Statistics
Notes
  • Danke für das SlideShare und die interessanten Informationen.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,227
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
14
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

Verteilte SoftwareEntwicklung 2011 - von klassischen Modellen bis Scrum und Social Coding

  1. 1. Verteilte Software Entwicklung 2011von klassischen Modellen bis Scrum und Social Coding 27. Juni 2011 Michael Lukas © 2011 Intland Software 1
  2. 2. Agenda• About Intland and codeBeamer• Live Demo• V-Model and Waterfall• Scrum & Kanban• Social Coding• Live Demo• Questions and Answers © 2011 Intland Software 2
  3. 3. Intlands 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 © 2011 Intland Software 3
  4. 4. Intland’s Distributed Development © 2011 Intland Software 4
  5. 5. What is codeBeamer• codeBeamer is an Application Lifecycle Management platform that helps development teams to manage their processes from requirements to release.• With centralized management of processes, users and projects, codeBeamer increases productivity, provides full traceability, improves visibility and reduces costs.• The collaboration offered by codeBeamer helps you to achieve up to a 50 percent increase in efficiency. © 2011 Intland Software 5
  6. 6. codeBeamer’s Operational Areas• Project, Process • Distributed Software Management Development• Requirements Management • Issue Tracking• Change Management • Ticketing System• Knowledge Management • Business Process• ITIL, SLA Management Monitoring © 2011 Intland Software 6
  7. 7. V-Model V-Model © 2011 Intland Software 7
  8. 8. Process Support Scrum, Kanban Waterfall, V-Process, Hybrid © 2011 Intland Software 8
  9. 9. V-ModelKey elements:• Process modules• Validation and Tracebility• Dependences between modules• Task that have to be executed• Iteration steps © 2010 Intland Software 9
  10. 10. Waterfall or V-Process in codeBeamer SW Rquirements SW Validation CB Releases,CB WIKI WIKI, Baselinesand Specificationdocuments 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. 11. Scrum & Kanban Scrum & Kanban © 2011 Intland Software 11
  12. 12. ScrumKey elements:• User stories• Product Backlog• Sprints• Scrum Roles (Scrum Master, Product Owner, Team) © 2010 Intland Software 12
  13. 13. Scrum Wizard © 2011 Intland Software 13
  14. 14. Scrum vs. V-Model Scrum V-ModellAdvantages Disadvantages Advantages Disadvantages•Light weighted •No overview about •Clear definition of • less flexibilityprocess/ project the whole process project phases •No clear Resourcemanagement •High communication • Complete overview disposition•Short iteration cycles, effort (daily Scrum) about the whole •Long iteration cyclesSprints •Less architectural process•Easy to learn overview •Industries proven © 2010 Intland Software 14
  15. 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 the 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 together and gives an complete overview about Scrum working items and V- Modell items. © 2010 Intland Software 15
  16. 16. Social Coding Social Coding © 2011 Intland Software 16
  17. 17. Centralized Work with Subversion, CVS, … Central repository © 2011 Intland Software 17
  18. 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. 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. 20. DVCS Fork/Pull-Request Workflow Example Blessed repository © 2011 Intland Software 20
  21. 21. DVCS Fork/Pull-Request Workflow Example Fork creation A Developer B Developer Blessed public public repository © 2011 Intland Software 21
  22. 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. 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. 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. 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. 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. 27. Live Demo Live Demo © 2011 Intland Software 27
  28. 28. Questions & Answers Questions and Answers © 2011 Intland Software 28
  29. 29. Thank you for your attention Thank you for your attention If you need further information please visit our homepage: www.intland.com www.javaforge.com HgEclipse: http://www.javaforge.com/project/HGEcodeBeamer Eclipse Studio: http://www.javaforge.com/project/CBES © 2010 Intland Software 29

×