take action - software practice

8/2/2019 Take ACTION - Software Practice

1/34

Take ACTION!A Software Engineering Practice

Institut Pertanian Bogor

Januari 2012


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


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


4/34


5/34

Traditional Software Engineering works

only when requirements are stable

Everything happens as one would expect


6/34

And if you already

have done this manytimes before


7/34

TIME

REQUIREMENT

DESIGN

CODE

TEST

DEPLOY

CANNOT PREDICT YOUR PLAN


8/34

TIME

REQUIREMENT

DESIGN

CODE

TEST

DEPLOY

CAN YOU SAY

50 % DONE ?

CAN YOU ?


9/34


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


11/34

If you achieve :1. Meet Requirement

2. On Time3. Within Budget


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


13/34

Agile


14/34


15/34

Short iteration enables

Motivation | Prioritization | Feedback


16/34

Continuous Feedback


17/34

Adaptive not predictive


18/34

Communicate

Effectively


19/34

Listen to their needs and establish trust


20/34

Tools


21/34

Dont reinvent

the wheelRemember the productivity

over technology


22/34Prepare PM Tools from the Beginning


23/34

Be Interactive with Customers


24/34

Be interactive when exploring the

requirement with customers


25/34

Gather Requirement through Collaborative

Workshop and Ask User Acceptance


26/34

Use prototype/wireframe toolsi.e Wireframesketcher, MockFlow, Visio, Balsamic


27/34

Out of the BoxFrom what and how to What If analysis


28/34

Explorer Artist

Judge Warrior

The Creative

Process


29/34


30/34

Notify

h ll


31/34

What went well,

What could be improved,

Lesson Learned


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-agile


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-agile


34/34

Thank you!

take action - software practice

Documents