verteilte softwareentwicklung 2011 - von klassischen modellen bis scrum und social coding

© 2011 Intland Software 1

Verteilte Software Entwicklung 2011

von klassischen Modellen bis Scrum und Social Coding

27. Juni 2011

Michael Lukas

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© 2011 Intland Software 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)

codeBeam

er

Source Code Engineering Features

CollaborativeTool Extensions

IntegrationsSCMs, IDEs

Prof. Services

ALM+Collaboration

Intland’s Distributed Development

© 2011 Intland Software 4

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

• Project, Process

Management

• Requirements Management

• Change Management

• Knowledge Management

• ITIL, SLA Management

© 2011 Intland Software 6

• Distributed Software

Development

• Issue Tracking

• Ticketing System

• Business Process

Monitoring

codeBeamer’s Operational Areas

V-Model

V-Model

© 2011 Intland Software 7

Process Support

© 2011 Intland Software 8

Scrum, Kanban Waterfall, V-Process, Hybrid

V-Model

Key elements:

• Process modules

• Validation and Tracebility

• Dependences between modules

• Task that have to be executed

• Iteration steps

© 2010 Intland Software 9

Waterfall or V-Process in codeBeamer

© 2011 Intland Software 10

Code

ComponentSpec.

ComponentTest

SW Design Spec.

SW Integration

SW Rquirements Specification

SW ValidationCB WIKI and documents

CB CMDB +Tracker

CB Projects

CB SCMGIT, eGIT, Gerrit, SVN

CB Releases, WIKI, Baselines

CB Reporting, CB Release

Integrated tools: HP QC,Hudson, build tools

Scrum & Kanban

Scrum & Kanban

© 2011 Intland Software 11

Scrum

Key elements:

• User stories

• Product Backlog

• Sprints

• Scrum Roles

(Scrum Master, Product Owner, Team)

© 2010 Intland Software 12

Scrum Wizard

© 2011 Intland Software 13

Scrum vs. V-Model

© 2010 Intland Software 14

Scrum V-Modell

Advantages

•Light weighted process/ project management •Short iteration cycles, Sprints•Easy to learn

Advantages

•Clear definition of project phases• Complete overview about the whole process•Industries proven

Disadvantages

•No overview about the whole process•High communication effort (daily Scrum)•Less architectural overview

Disadvantages

• less flexibility•No clear Resource disposition•Long iteration cycles

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.

© 2010 Intland Software 15

Requirements, Tasks, Test

SCM, Builds, Project overview

User Stories,Product Backlog, Sprint Plan,

Kanban,

CBRelease

In the release, all artifacts are combined together and gives an complete overview about Scrum working items and V-Modell items.

ScrumV-Model

Social Coding

Social Coding

© 2011 Intland Software 16

Centralized Work with Subversion, CVS, …

© 2011 Intland Software 17

Centralrepository

DVCS Central Shared Repository

© 2011 Intland Software 18

sharedrepository

•Offline Work•Merge•Speed

A Developer local

B Developerlocal

C Developerlocal

DVCS Central Shared + Private Repository

© 2011 Intland Software 19

sharedrepository

•Offline Work•Merge•Speed

A Developer local

B Developerlocal

C Developerlocal

repository

DVCS Fork/Pull-Request Workflow Example

© 2011 Intland Software 20

Blessedrepository

DVCS Fork/Pull-Request Workflow Example

© 2011 Intland Software 21

Blessedrepository

A Developer public

B Developer public

Forkcreation

DVCS Fork/Pull-Request Workflow Example

© 2011 Intland Software 22

Blessedrepository

A Developer public

B Developer public

A Developer local

B Developerlocal

IntegrationManager(s)

Creating a local clone

DVCS Fork/Pull-Request Workflow Example

© 2011 Intland Software 23

Blessedrepository

A Developer public

B Developer public

A Developer local

B Developerlocal

IntegrationManager(s)

Starting a Pull-request

Checkin changes Pull-request

DVCS Fork/Pull-Request Workflow Example

© 2011 Intland Software 24

Blessedrepository

A Developer public

B Developer public

A Developer local

B Developerlocal

IntegrationManager(s)

Merging changes in blessed repositoriy

Merge

DVCS Fork/Pull-Request Workflow Example

© 2011 Intland Software 25

Blessedrepository

A Developer public

B Developer public

A Developer local

B Developerlocal

IntegrationManager

Share changeswith the team

GIT Workflow with Forks and Pull Request

© 2011 Intland Software 26

Bob DeveloperLocal Repository

Integrationmanager

Bob DeveloperRemote Repository

BlessRepository

ForkPull Request

Fetch Push

codeBeamer Server

Live Demo

© 2011 Intland Software 27

Live Demo

Questions & Answers

© 2011 Intland Software 28

Questions and Answers

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/HGE

codeBeamer Eclipse Studio: http://www.javaforge.com/project/CBES

© 2010 Intland Software 29