Take ACTION!

A Software Engineering Practice

Institut Pertanian Bogor Januari 2012

2007 2009
Process Engineer Team Leader at Sigma Cipta Caraka (TELKOM)

2009 2011
BI & Collaboration Analyst at Coca-Cola Bottling Indonesia

2010 - Present
Co-Founder of KartuMuu.com

2011 Present
Sales Analyst Mgr at Danone Baby Sari Husada

Software Engineering is the application of a systematic, disciplined, quantifiable approach to development, operation, and maintenance of software: that is the application of engineering to software
IEEE Standard Computer Dictionary

WHY?

Traditional Software Engineering works only when requirements are stable

Everything happens as one would expect

And if you already have done this many times before

CANNOT PREDICT YOUR PLAN

REQUIREMENT DESIGN

TIME

CODE TEST DEPLOY

CAN YOU ?
REQUIREMENT DESIGN

TIME

CODE TEST DEPLOY

CAN YOU SAY 50 % DONE ?

A BETTER WAY REQUIREMENT DESIGN CODE TEST DEPLOY

TIME

WE CAN SAY 40 % FROM 100 % USABLE

Traditional software engineering cause

high cost of change

Traditional
1. 2. 3. 4. Trace defect Fix defect Regression test Deploy Find defect as Soon as possible causes lower costs of defect

Cost of Change

Requirement

Design

Code

Test

Deploy

Time

If you achieve :
1. Meet Requirement 2. On Time 3. Within Budget

How to be Successful? Take ACTION!

A C T I

gile ommunicate effectively

ools
nteractive with customers

O ut of the box thinking N otify stakeholder

Agile

Short iteration enables

Motivation | Prioritization | Feedback

Continuous Feedback

Adaptive not predictive

Communicate Effectively

Listen to their needs and establish trust

Tools

Dont reinvent the wheel

Remember the productivity over technology

Prepare PM Tools from the Beginning

Be Interactive with Customers

Be interactive when exploring the requirement with customers

Gather Requirement through Collaborative Workshop and Ask User Acceptance

Use prototype/wireframe tools

i.e Wireframesketcher, MockFlow, Visio, Balsamic

Out of the Box

From what and how to What If analysis

Explorer Judge

Artist Warrior

The Creative Process

Notify

What went well, What could be improved, Lesson Learned

Early notification will help you manage expectation from stakeholders

Reference
http://www.slideshare.net/Siddhi /intro-to-agile http://www.slideshare.net/cperro ne/passionate-teams-cooperativecustomers-388318 http://www.slideshare.net/dancin gmango/better-faster-cheaperlean-and-agile-approaches-to-itdevelopment-presentation

Thank you!