Project dev

Project development:methodology & practice

Presented by: Kenny LinDate: 2013. 2. 1

Agenda

Project management: Waterfall

VS. Agile

Scrum methodology

Proposed practice in Moxa IT:

open discussion

Traditional project development(a. k. a. Waterfall)

Assumption & philosophy behindwaterfall methodology• Plan driven, sequential process• Problems are well defined • Change should be limited (if not

forbidden)• Project/product dev. is similar to

product manufacturing

What does it mean to be agile (1)

• Iterative and incremental development: faster delivery/feedback cycle

• Split and prioritize : small batch size


• Favor an adaptive, exploratory approach -- just like programming

• Collaboration and intense communication• Embrace change


• Early integration• Automated testing & Test Driven

Scrum: the most popular agile methodology

Scrum Basic Concepts

• Product Backlog• Sprint

• Sprint Backlog• Scrum team

Scrum’s key unit : Sprint

• A short-duration, time-boxed iteration• Starts with pre-defined goal• Finishes with ready-for-production

increments

Scrum : Sprint based dev.

• Fixed length• No goal-altering changes in Sprint

Scrum : Sprint backlog (tasks)

Let’s run it our own way (1)One-month Sprint

• Sprint planning• Split & Prioritize• Specify the goal and

targeted backlog(s)• List tasks with owner • Pre-define of done


• Sprint execution• Weekly Scrum• Intense communication with product

owner• On-the-spot mentoring (by Kenny)• Continuous integration and testing (SVN)


• Sprint review• Demo & user (stake holder) feedback• Code review• Process review

• “What we have done great, and what we should avoid doing again?”

Let’s run it our own way (2)The Scrum Team

• Product Owner• Acted by department manager• Splits and prioritizes backlogs• Clarifies requests and answers questions

during sprint execution

• Scrum Master: Kenny• Development Team : Kenny & the team

Confidential

Thank You

Technology

Project dev