How does it feel like to adopt Agile in a Singapore SME?
What are the lessons learned along the way?
This is a story of excitements and struggles Titansoft being through in last 10 years, from a small 5 people team to 150 people across different countries.
15. How to keep the world safe without heroes
What we have tried up till 2016
- Delegation
- Job Rotation
- Training
- Coaching
- Collective Code Ownership
- Operates in unit of team
24. You are too slow!
How to Deliver Software Faster?
25. How To Deliver Software Faster?
What we have tried up till 2016
- Change Organization Structure
- Back End / Front End Specialist
- Production / Development Teams
- End to End Teams
- Technical Practice
- Individual / Team Code Ownership
- Continous Integration
- Change Scope
-Minimum Viable Product (MVP)
- Secret Developer Toolbox (No test, hard-code, etc) #1
#1. Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
31. Age of
Heroes
2005 - 2008
Age of
SOPs
2012 - 2013 2014 - Current
Age of
My Turfs
2009 - 2011
Different Ages as We Progress
32. Organization Chart
Matrix Structure
2 Bosses
General
Manager
PMO
Project
Mgr.
Project
Mgr.
…
Front End
Dev.
Front End
Front End
…
Back End
Dev.
Back End
Back End
…
QA
QA
QA
…
Creative IT HR
35. Product Downtime Trend
2007 2008 2009 2010 2011 2012 2013
Monthly Average Downtime (Minutes)
Downtime increase over
200%
36. There must be bad apples!
How to Measure Productivity?
37. How to Measure Productivity?
What we have tried up till 2016
- Time Sheets
- Team KPI
- Department KPI
- Kanban
- Measure Development Outputs
- Measure Process Efficiency
- Measure Product Outcome
43. Age of
Heroes
2005 - 2008
Age of
SOPs
2012 - 2013
Age of
Post-Its
2014 - Current
Age of
My Turfs
2009 - 2011
Different Ages as We Progress
44. General
Manager
Product
Dev. 1
End to
End Team
Product
Developer
Product
Developer
…
End to
End Team
Product
Developer
Product
Developer
…
Product
Dev 2
End to
End Team
Product
Developer
Product
Developer
…
Creative
Product
Dev…
IT HR
Elite Team
Organization Chart
Product Oriented
Departments
45. Product Incidents Trend
2007 2008 2009 2010 2011 2012 2013 2014 2015 2016
Monthly Average Incidents
Reduced by 40%, incidents are
mostly from old projects
50. How to Communicate Better?
What we have tried up till 2016
- Accept Failures
- Retrospectives
- Facilitation
- Visualization
- Recognize Assumptions
- Satir Iceberg Model
- Open Space Technology
52. Age of
Heroes
2005 - 2008
Age of
SOPs
2012 - 2013
Age of
Post-Its
2014 - Current
Age of
My Turfs
2009 - 2011
Different Ages as We Progress
53. Top Keywords in Our Journey
Age of
Heroes
Age of
My Turfs
Age of
SOPs
Age of
Post-Its
Commitment
Req. Change
Bug Fix
Urgent
Support
Responsibility
Plan
Schedule
Rewrite
Best Practice
Accountability
Procedure
Training
Efficiency
Metric
Ownership
Self-organizing
Effective
Team
Assumption
54. Top Emotions in Our Journey
Age of
Heroes
Age of
My Turfs
Age of
SOPs
Age of
Post-Its
Interesting
Frustrated
Excited
Proud
Nervous
Excited
Interesting
Content
Tired
Nervous
Tired
Surprised
Frustrated
Nervous
Interesting
Excited
Interesting
Happy
Thoughtful
Content
55. Tools We Explored Along the Way
Product
People
Process
MBTI
Kanban
UX
DISC
ISO
27001
KPI
PMP
Facilitation Coaching
ITIL
One Page
Concept
Technical
Practices
Continuous
Integration
HR Practice
Scrum
Agile
Data
Science
Satir
Model
56. Metrics for People, Product and Process
Money
Users
Frequency of Release
Interactions within team
Interactions with other teams
Product
57. Metrics for People, Product and Process
Money
Users
Frequency of Release
Interactions within team
Interactions with other teams
Product
Lead Time
# of Reworks
# of Retrospectives
% of time on Manual Work
% of time on Repetitive Work
Process
58. Metrics for People, Product and Process
Laughter
Post-Its Usage
HR Turnover Rate
Noise Level in Office
Topic of chitchat
People
Money
Users
Frequency of Release
Interactions within team
Interactions with other teams
Product
Lead Time
# of Reworks
# of Retrospectives
% of time on Manual Work
% of time on Repetitive Work
Process
64. Summary
1. Always rely on a team, not individuals.
(When sustainable is what you want)
2. Software delivery is easy, maintenance is the hard part.
(If your product is successful)
3. What you measure will improve.
(Or at least it appears so)
4. There are millions shades of grey.
(Besides black and white)
5. “When you're finished changing, you're finished.”
Age of
Heroes
2005 - 2008
Age of
SOPs
2012 -2013
Age of
Post-Its
2014 -
Current
Age of
My Turfs
2009 - 2011