Unleash your team's creativity with lean by Karim Aouadi

Copyright © Institut Lean France 2013

3 & 4 October, 2013
Paris, France

Unleash your team’s creativity
with the lean approach
Karim AOUADI
Nicolas MOUSSON


Summary
•
•
•
•
•
•

Case study
What’s creativity ?
Industrialization of manufacturing process
Having philosophy
How to measure value creation?
Conclusion

Unleash your’s team creativity using lean approach- Karim AOUADI & Nicolas MOUSSON

2


Summary
•
•
•
•
•
•

Case study
Having philosophy
Conclusion


3


Starting
• Goal of the project
 Development of the business management platform (middle-

sized company, founded in november 2011)

• Motivation and challenges
 For team project
 Building a SaaS solution and sell it to multiple customers
 Getting skilled on cloud technologies
 Setting up an agile process

 For customer
 Facing problems with his current information system and growth of activity
Customer reminder is taking up too much time
 Limited users…
 Technical infrastructure need to be better managed
 Business proposals and invoices are not clear
 Business proposals are created with Microsoft Office

4


• Technical choices
 A proven technical ecosystem to prototype and produce quickly

and master development and production costs
 Software development platform
 Ruby on Rails used by internet companies to quickly build prototypes and

ease deployment

 Cloud production platform(Paas)
 Heroku’s service streamlined for application deployment and management

• Initial team
 2 developers

 C… CEO


5


Phases of SaaS platform
development
1.
2.
3.
4.
5.
6.
7.

Failure
A new start
Delivery of the sales module
Final delivery of the sales module
Delivery of purchases module
Delivery of production operational platform
Delivery of stocks module

Overview
of
situation

Case study

New
strategy

Lessons
learned


6


Phase 1 : Failure
• Overview of situation after 5 month
 Customer trust is lost (no delivery)

 Team does have any work

• Strategy
 Reorganization

 Develop real business analysis
 Planned delivery within 1 month

• Lessons learned
 Customer trust is very important
 Understand customer’s functional requirements


7


Phase 2 : A new start
• Overview of situation after 1 month (April 2012)
 Customer trust is back
 A prototype has been delivered
 The arrival of a new employee and departure of a former partner

• Strategy
 Business analysis with customer
 UX at the heart of our creation process
 Agile process (Scrum board, prioritizing requirements)

• Lessons learned
 An early failure may be beneficial, allowing a new start
 Building a team

8


Phase 3 : Delivery of sales
• Overview of the situation after 2 month
 Product delivery on the cloud

• Strategy
 New business requirements for payment and financial management
need new contributors
 Store manager for payments
 CPA(Certified Public Account)

 Setting up an industrialization process to deliver
 UI and Usability are major challenges for the project team
 Time investment
 Setting up UI design principles to improve UX

• Lessons learned
 Usability
 Product quality

9


Phase 4 : Final delivery of sales
• Overview of the situation after 3 month(April 2012)
 Delivery of invoice payment process to monitor cash flow

 The platform gets improved UI Design to facilite the work

• Strategy
 Continuous improvement of business processes, in order to

provide a purchase order
 Set up a development approach centered on business design
 Domain Driven Design

• Lessons learned
 Industrializing software deployment (Schema)
 Industrializing software development
 Changes in business processes

10

Industrializing software deployment

Test Apps

Production Apps

HEROKU CLOUD PaaS
Local development

Prod
Test
• V2.x.x
• V1.x.x

GIT

Distributed revision
control(SCM)
CLOUD SCM

GITHUB


11


Phase 5 : Delivery of purchases
• Overview of the situation after 3 month(December 2013)
 Purchases module has been delivered

 Business growth imply changing the data model and thus setting

up a standard data transfer procedure

• Strategy
 Scaling up platform to manage many organizations
 Setting up a multi-tenant platform to avoid physical infrastructure replications

 Planned delivery of operational platform: early January 2013

• Lessons learned
 Industrializing data transfer
 Ensure data quality on each delivery


12


Phase 6 : Delivery of production
operational platform
• Overview of the situation (Januray 2013)
 Two companies are using the business services offered by our

platform.
 Multi-tenant software infrastructure is operational

• Strategy
 Business analysis of stock management processes
 Improve the flexibility usage of platform (Multi document printing)
 Technical optimization
 Designing a new rendering engine

• Lessons learned
 Multi tenant cloud platform

13


Phase 7 : Delivery of stocks
• Overview of the situation after 4 month (May 2012)
Company’s modules

Sales

Purchases

C…………

X

X

K………….

X

Stocks

X

X

 C.. company has launched a team reorganization, the appointment of a
new employee to accelerate the billing process
 The accounting firm is interested in seeing accounting and financial
services implemented on platform
 Implementation of modules management to configure the services
requested

• Strategy
 Business analysis of accounting rules and processes
 Creating a data sample to futher test the implementation of business rules

14


• Lessons learned
 Industrialization of the development process
 Make use of production operational data to test during development

 Ensure data quality
 Analyze production data (accuracy, interpretability, consistency)

 Performance
 Optimizing the data model
 UX (display only useful data)

 Usability and design
 Check behavior of the end-user to the scenario initially planned (schema)
 Analyze demands and comments from end-users
 Setting up restrictions on some implemented features to create user’s

reaction

 Designing platform
 Reduce development time (30%)

 Invest more resources in the business analysis process (70%)


15


Accountant must record
accounting entries at the end
of each month

>> Selected start date and
end date to display all
invoices of current month

Basic design

16


Accountant must record
accounting entries at the end
of each month

>> Click to display all
invoices of current
month

Setting up the usability

17


The SaaS operational platform
Sales management
Purchases management
Stocks management
Accountants management(In progress)


18


Summary
•
•
•
•
•
•

Case study
Having philosophy
Conclusion


19


What is creativity?
• Definition
 Ability to offer solutions that will be a source of
value creation
 Is based on client requirements
 Trust
 Quality
 Time

 Intuition


20


Summary
•
•
•
•
•
•

Case study
Having philosophy
Conclusion


21


Industrialization of the
manufacturing process
• Aim of this standardization
 Ensure the quality of your Saas Platform
 A business – oriented design(DDD)
 Procedures for data transfert
 Procedures for deployment
 Procedures for quality data analysis
 Reduce development time to
 Increaskng business analysis and modeling
 Improving usability
 Improving productivity of our customers’ staff

22


Summary
•
•
•
•
•
•

Case study
Having philosophy
Conclusion


23


Having a philosohy

Continuous
improvements

Usability

Visibility

Modeling

Quality

Team


24


Usability
• Ease of use of our platform is the heart of
our concerns
• The more rules you set up, the more
people try to break them
• Reduce the learning curve of our product
• Get inspired by the philosophy of public
platforms like Facebook, Google

25


Modeling
• Do not hesitate to break and rebuild a
model or a design
• Get out of the software overbuilding model
• Building something really simple is really
complex
• Do team work when analysis and modeling
business

26


Quality
• Periodically check data entered by endusers
• Analyze the behavior of end-users
• Check that things are correct
• Provide business services, easy to use for
your customers


27


Visibility
• Show things to your end-users periodically
• Avoid explanation that might be too
abstract for end-users, build and show
them a prototype instead


28


Continuous improvement
• Replicate what has been working so
far(after validation on the operational
platform with end-users)
• Develop a resultat-driven culture
• Learn from failures
• Continously solve problems


29


Summary
•
•
•
•
•
•

Case study
Having philosophy
Conclusion


30


BA /Modeling
UI Design

Manufacturing
code

Working time

Value
stream

Operational
costs

Delivery


31


BA + Modeling + UI Design

70%
20%

of our time


32


Manufacturing code
• The number of lines of code has been
decreasing after each delivery of new
version Platform
Delivery
Lines created
Lines deleted

Sales
283 000
77 900

Purchases
54 000

Stocks
64 000

66 329

Accounts
……

40 000


33


Delivery
• Delivery phase takes less than 30 minutes
• 1 delivery per month


34


Operational costs
• Operational costs are stable, depending of
the number of potentially new customers
 Our SaaS Platform is based on service
Heroku PaaS
Companies

Cost

Up to 10

20 € / month


35


Working time

3.5 days
per
week

36


Value stream / Cash flow
350000
300000
250000
200000
150000

Sales

100000

Cash

50000
0


37


Summary
•
•
•
•
•
•

Case study
Having philosophy
Conclusion


38


Conclusion
• A good sense
• Rigour


39


More about Lean IT on:
www.lean-it-summit.com

Unleash your team's creativity with lean by Karim Aouadi

More Related Content

What's hot

Viewers also liked

Similar to Unleash your team's creativity with lean by Karim Aouadi

More from Institut Lean France

Recently uploaded

Unleash your team's creativity with lean by Karim Aouadi