8/2/2019 Take ACTION - Software Practice
1/34
Take ACTION!A Software Engineering Practice
Institut Pertanian Bogor
Januari 2012
8/2/2019 Take ACTION - Software Practice
2/34
2007 2009
Process Engineer Team Leader
at Sigma Cipta Caraka (TELKOM)
2009 2011BI & Collaboration Analyst
at Coca-Cola Bottling Indonesia
2010 - Present
Co-Founder of KartuMuu.com
2011 Present
Sales Analyst Mgr
at Danone Baby Sari Husada
8/2/2019 Take ACTION - Software Practice
3/34
Software Engineering is the
application of a systematic,disciplined, quantifiable approach to
development, operation, and
maintenance of software: that is theapplication of engineering to
software
IEEE Standard Computer Dictionary
8/2/2019 Take ACTION - Software Practice
4/34
8/2/2019 Take ACTION - Software Practice
5/34
Traditional Software Engineering works
only when requirements are stable
Everything happens as one would expect
8/2/2019 Take ACTION - Software Practice
6/34
And if you already
have done this manytimes before
8/2/2019 Take ACTION - Software Practice
7/34
TIME
REQUIREMENT
DESIGN
CODE
TEST
DEPLOY
CANNOT PREDICT YOUR PLAN
8/2/2019 Take ACTION - Software Practice
8/34
TIME
REQUIREMENT
DESIGN
CODE
TEST
DEPLOY
CAN YOU SAY
50 % DONE ?
CAN YOU ?
8/2/2019 Take ACTION - Software Practice
9/34
8/2/2019 Take ACTION - Software Practice
10/34
Traditional software engineering cause
high cost of change
Requirement Design Code Test Deploy
Cost of
Change
Time
1. Trace defect
2. Fix defect
3. Regression test
4. Deploy
Find defect as
Soon as possible
causes lower costs
of defect
Traditional
8/2/2019 Take ACTION - Software Practice
11/34
If you achieve :1. Meet Requirement
2. On Time3. Within Budget
8/2/2019 Take ACTION - Software Practice
12/34
How to be Successful? Take ACTION!
A gile
C ommunicate effectively
T ools
I nteractive with customersO ut of the box thinking
N otify stakeholder
8/2/2019 Take ACTION - Software Practice
13/34
Agile
8/2/2019 Take ACTION - Software Practice
14/34
8/2/2019 Take ACTION - Software Practice
15/34
Short iteration enables
Motivation | Prioritization | Feedback
8/2/2019 Take ACTION - Software Practice
16/34
Continuous Feedback
8/2/2019 Take ACTION - Software Practice
17/34
Adaptive not predictive
8/2/2019 Take ACTION - Software Practice
18/34
Communicate
Effectively
8/2/2019 Take ACTION - Software Practice
19/34
Listen to their needs and establish trust
8/2/2019 Take ACTION - Software Practice
20/34
Tools
8/2/2019 Take ACTION - Software Practice
21/34
Dont reinvent
the wheelRemember the productivity
over technology
8/2/2019 Take ACTION - Software Practice
22/34Prepare PM Tools from the Beginning
8/2/2019 Take ACTION - Software Practice
23/34
Be Interactive with Customers
8/2/2019 Take ACTION - Software Practice
24/34
Be interactive when exploring the
requirement with customers
8/2/2019 Take ACTION - Software Practice
25/34
Gather Requirement through Collaborative
Workshop and Ask User Acceptance
8/2/2019 Take ACTION - Software Practice
26/34
Use prototype/wireframe toolsi.e Wireframesketcher, MockFlow, Visio, Balsamic
8/2/2019 Take ACTION - Software Practice
27/34
Out of the BoxFrom what and how to What If analysis
8/2/2019 Take ACTION - Software Practice
28/34
Explorer Artist
Judge Warrior
The Creative
Process
8/2/2019 Take ACTION - Software Practice
29/34
8/2/2019 Take ACTION - Software Practice
30/34
Notify
h ll
8/2/2019 Take ACTION - Software Practice
31/34
What went well,
What could be improved,
Lesson Learned
8/2/2019 Take ACTION - Software Practice
32/34
Early notification will help you manage
expectation from stakeholders
R f
http://www.slideshare.net/Siddhi/intro-to-agilehttp://www.slideshare.net/Siddhi/intro-to-agile8/2/2019 Take ACTION - Software Practice
33/34
Reference http://www.slideshare.net/Siddhi
/intro-to-agile
http://www.slideshare.net/cperrone/passionate-teams-cooperative-
customers-388318
http://www.slideshare.net/dancin
gmango/better-faster-cheaper-lean-and-agile-approaches-to-it-
development-presentation
http://www.slideshare.net/Siddhi/intro-to-agilehttp://www.slideshare.net/Siddhi/intro-to-agile8/2/2019 Take ACTION - Software Practice
34/34
Thank you!