Run hybrid agile + waterfall nguyen vu hung scrum-day2013

Attribution-ShareAlike CC BY-SA
Nguyễn Vũ Hưng
ScrumDay Vietnam 2013/10/06, Hanoi
FaceBook/Email: vuhung16plus@gmail.com
Tel:0904-28-7878
Run
Agile + Waterfall

2013/10/06 ScrumDay Vietnam 2013
FPT Aptech, Hanoi, Vietnam
2Attribution-ShareAlike CC BY-SA
Agenda
✔ Introduction
✔ Experimental Purposes
✔ Agile Manifesto
✔ Conclusions
✔ Project Requirements
✔ Notes on Customers
✔ SDLC
✔ Organization and Communication
✔ Planned/Actual Process
✔ Rough Estimation
✔ First Planning
✔ Requirement Definition
✔ Prototype
✔ Design
✔ Coding/Unit Test
✔ Integration Test
✔ Bugfix/Test/Review
✔ TiDD
✔ Results/Looking Back
✔ Lesson Learned
✔ Q&A
①
②
③
④

Introduction
● Nguyễn Vũ Hưng
● Project Manager/PMO
● Japanese SI/IT Company
● In love with FOSS and Agile
● Contact Info
● Facebook/Email:
– vuhung16plus@gmail.com
● Tel: 0904-28-7878

What I am Looking for
● Balance between
● Agile and Waterfall
– Old and New
– East and West
– Direct and Indirect
● Big and Small
● East and West
● The best SDLC
● In general
● Suits my needs
● Try something new?

Manifesto for Agile Software Development
●
プロセスやツールよりも個人と対話を、
●包括的なドキュメントよりも動くソフトウェアを、
●契約交渉よりも顧客との協調を、
●計画に従うことよりも変化への対応を、

Today's Topics
Transition: Waterfall → Agile ＋
Waterfall
Manage Changes
Share Experience

Conclusions
● Yes, Agile and Waterfall can be mixed
● Overlapped phases
● A working product is
important
Quy trình thực tế
Estimate
Planning
Requirement Gathering (RD)
Prototype
Basic/Detail Design
Coding/Unit Test (CD/UT)
Integration Test (IT)
Alpha 1, 2, Beta 1, 2, 3, 4, RC, Final
System Test (ST)
User Acceptance Test (UAT)

Project Requirements (business)
● Copycat existing product
● To develop a product that is similar to an existing one
● 40-ish main features
● Customer is unclear on what they must do
● 10-ish constraints
● Time-to-market
● Almost fixed
● First output
● Rough estimation (time and cost)
● Copycat existing product
● To develop a product that is similar to an existing one
● 40-ish main features
● Customer is unclear on what they must do
● 10-ish constraints
● Time-to-market
● Almost fixed
● First output
● Rough estimation (time and cost)

Nhận định khách hàng
● Tham lam
● Muốn nhiều yêu cầu
● Bảo thủ
● Nhật Bản, Á Đông
● Bẫy kinh nghiệm
●
Tuổi trung bình PMO: 　 U50
● Mô hình top-down
● Áp đặt
● Tổ chức/quy trình cũ (waterfall là duy nhất!)

Software Development Lifecycle (SDLC)

Project Orgnization/Communication
● Product Owner
● Requirement Supplier
● Project Management Officer
● Development Team

Planned Process (1)
● Top-down
● Waterfall
● Process exit condition
● RD→Design→CD/UT→IT

Planned Process (2)
● Top-down
● Waterfall
● Process exit condition
● RD→Design→CD/UT→IT
FAILED

Rough Estimation
● Function Point (FP)
● Lack of information
● Lack of historical data
● Less accurate
● Actual Estimation Method
● Not available: Use case, story points...
● Use an FP variant
– # of screens and the # of input/output on each screen
– Effort (man-day) needed to complete a screen
● Requirement, Design, Coding/UT, IT
– Consolidate above efforts
# Sample FP estimation:

Planning
Công số theo người
Kế hoạch phát triển
dự kiến theo tháng

Actual Progress
● It is unique for each project
● Re-Plan is occurred until the end of the project

Requirement Gathering (RD)
● Scope creep
● Greedy customer: They wants everything
● Time constraints
● Company regulation: RD→Design→CD/UT
● Could not get approval on RD
● This is the weakness of Waterfall
● Actual progress
● Prototype, coding while doing RD/CR, or
● Do all process in parallel

Prototype
● A working deliverable
● Helps customers have an idea on what they will have
● When RD is not finished
● Sub steps
● Balsamiq prototype
● Photoshop
– CSS, HTML, PNG
● PHP
# Screenshot is taken from another project

Design
● Required deliverable
● Basic/Detail Design
● Prototype
● Screen design
● Data design
● Waste of time with none or little future use

Coding/Unit Test
● Training
● Proof of Concept
● Focus on complicated modules
● Technical feasibility to reduce risks
● Evaluate performance of PoC code
● Coding
● Every screens (frontend) and commands (backend)
● When the design is done
● Customer Review/Update: #1, #2, #3,...
● Unit test

Integration Test
● Put software components together
● Backend/frontend
● With network devices
● Various software configurations
● Various Hardware configrations
● Test on multiple versions
– Network devices
– Frontend server
– Backend services

Sprints: Bugfix/Test/Review
● Alpha, Beta, RC, Final
● 8 sprints
● Customers/Users involved testing
● One Sprint per a week
● Customers review (→retro)
● Test
● Bugfix
● Enhencement
# 1 week/sprint
# 1 week/sprint

Ticket-Driven Development (TiDD)
TicketTicketTicketTicket

Actual Results
● One month behind schedule
● Design: 100% rework
● Overlapped processes
T4 T5 T6 T7 T8

Lessons Learned
● Waterfall
● Consumes more time than Agile
● Not flexible
● Predictive (Waterfall) not as good as adaptive (Agile)
● Clear exit condition is crucial for both
● Free test and CI can cover good quality
● Take risk and take responsibility
● Ticket-Driven Development (TiDD)
● Continuous Integration (not really)
● "Không sáng tạo với khách hàng Nhật"?

My Concerns and TODOs -;(
● Does it really works?
● Does project size matter?
● What are the side effects on transition?
● Where are the tipping points for innovation?
● Redmine + Hudson
● Redmine + Jira/TestLink
● ISO/IEC 15504: Information Technology - Process Assessment
● PMBOK 5th/ISO 21500: Guidance on Project Management
● "Agile" Maturity, as in Capability Maturity Model

Q

Run hybrid agile + waterfall nguyen vu hung scrum-day2013

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Mehr von Vu Hung Nguyen

Mehr von Vu Hung Nguyen (20)

Run hybrid agile + waterfall nguyen vu hung scrum-day2013