Agile Product Management

Looking in from the outside - Scenario-guided design, ALM and OSLC

Session Type: 
Standard [35 minutes]
Speakers

In 2008, the Jazz team set out on a journey to provide a world class ALM solution that allowed for loosely coupled integrations and an experience of 'surfing the ALM web of related artifacts.' In 2012, the solution for Collaborative Lifecycle Management received the highest marks in the Forester ALM wave. The team achieved this transformation by having an open architecture based on web standards, building a community for open integrations, and using a user-centric, lifecycle scenario to guide our choices about the experience.

Schedule info

Time slot: 
26 March 14:15 - 14:50
Room: 
Back Bay
Status: 
Accepted

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Requirements On The Verge Of A Nervous Breakdown

Session Type: 
Standard [35 minutes]
Speakers

Agile puts enormous strains on the people responsible for software requirements:

  • How do they get just enough requirements in time for the next sprint?
  • How do you pack enough information into the requirements to provide meaningful guidance?
  • Will you ever provide meaningful guidance for outsourcing partners?
  • How do you spin off additional artifacts for governance and compliance?
  • How do you re-purpose the information in the requirements for other audiences?
  • Do you ever get a chance to do retrospectives on requirements?

Schedule info

Time slot: 
26 March 11:15 - 11:50
Room: 
Back Bay
Status: 
Accepted

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Agile Development using Visual Requirement Definition and Management Methods

Session Type: 
Standard [35 minutes]
Speakers

The advantages of applying lean and agile techniques to software design and development activities of are now well established and understood in IT focused organisations.

Often many IT organisations who have implemented agile techniques continue to struggle because they either do business analysis activities through a waterfall process or skip upfront requirements analysis completely as proposed by agile purists. How do we use requirements definition and management in an agile process?

Schedule info

Status: 
Declined

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Testing of Eclipse RCP based products

Session Type: 
Standard [35 minutes]
Speakers

Stability is a key requirement for an established product. Of course, software is never bug free, but bugs being fixed must stay so in later releases. As manual testing is error prone and quite expensive, consequent automated testing is the logical implication.

Especially in the case of Eclipse RCP applications and Plug-Ins, being delivered to different target platforms and installed into many possible client configurations, migration and system testing is also important.

Schedule info

Status: 
Declined

Audience

Track: 
ALM Connect
Experience level: 
Beginner

How Agile is the team? - Measuing Agile Maturity using effective but simplified team self assessment technique

Session Type: 
Tutorial [3 hours]
Speakers

The proposed topic would help organizations who have adopted agile methodology for delivering time sensitive business critical applications. The paper would demonstrate a very simiplified team self assessment framework to decide "How Agile is the team?".

There are self assessment tools or questionnaires in the market, they are expensive and require customization to meet the organization specific requirements. The technique proposed is very simple, currently using excel to capture the survey results from Scrum Master, Analysts, Developer and Testers in the Agile standing team.

Schedule info

Status: 
Declined

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.