Med projektdeltagare utspridda över ett geografiskt område stod Sellegi inför en utmaning när man skulle utveckla sin produkt SELLEGI ACT. Eftersom produkten dessutom var en nyutveckling var time to market en kritiskt faktor. Eric Lundquist, CEO Sellegi berättar om hur man effektiviserade utvecklingsmiljön genom att implementera en plattform för Engineering Collaboration och hur man också skapade nöjdare kunder. Talare: Eric Lundquist, CEO, SELLEGI Besök http://smarterbusiness.se för mer information.

1. Sellegi – Innovation and Engineering Collaboration
Eric Lundquist
CEO
Sellegi Technologies AB

2. Who we are
• We are experts in visual modeling
• We believe in the power of
visualization and abstraction
• We offer innovative project
management through project modeling

3. UP TO 80%
OF BUDGETS ARE
CONSUMED
FIXING SELF-INFLICTED
PROBLEMS. Dynamic Markets Limited 2007 Study

4. Sellegi ACT
– A project modeling tool
Key Capabilities:
• Managing dependencies
• Meet the schedule
• Fact based – real data
• Know what will be delivered
• Parallel impact analysis
• Early risk identification
”Making complex projects simple”

5. 25% – 40%
OF ALL SPENDING ON
PROJECTS IS WASTED
AS A RESULT OF
REWORK. Carnegie Mellon

7. 40%
OF PROBLEMS
ARE FOUND BY
END USERS. Gartner

9. Background
• Distributed team
• Information in e-mails and
documents
• Poor traceability
• Lack of transparency
• Coordination overhead

10. Challenges
• Customer expecting fast and
correct deliverables
• Need of early warning on the
development status
• Very high quality expectation
• Limited resources could be
dedicated to this

11. What we needed
• Process support - “our way”
• Planning and change support
• Seamless and transparent
communication
• Happy developers
• Low overhead
• Cost efficient

12. How we solved it
• IBM Rational Team Concert
– Web based tool
– Adapted Scrum process template
– Role based process (PM, Scrum
master, Developer and Admin)
– Iteration planning
– Integrated stories, code changes
– Information sharing through live
dashboard
– Integrated with development
environment (Eclipse)

14. Our way of working
1. Ideas (Whiteboard)
2. Initial architecture (RSA) 12. All persons involved monitor Dashboard with real-time
progress and changes – transparency / openness
3. Create project 13. Perform re-planning and change management
4. PM creates timeline with iterations 14. Repeat for all iterations
5. PM creates product backlog
6. Associate stories with iterations 15. Release involves additional testing and documentation.
RTC guides to changes since the previous release.
16. Release
7. Developers work on stories from iterations
8. Developers update a story by setting status and
associating changed code
9. A developer assigns an implemented story to tester
10. Tester checks that story works
11. Repeat for all stories in iteration

15. Extended collaboration
• Recently we have been extending
integrations of Sellegi ACT to the
Jazz platform
• Open commercial software
development.
• We have been able to influence
priorities
• We can see progress and
download builds as they are
available.

16. Experience
• Intuitive usage
• No context / tool switch for the
technical staff
• Specific release support on
changes helps focusing testing
and documentation leading to
fewer errors
• Quick reaction to changes

17. Conclusion
• Satisfied customer through better
communication and actions
• Happy developers
• High productivity / leverage
leading to fast time-to-market

18. Questions?