Project dev

238 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
238
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Project dev

  1. 1. Project development: methodology & practice Presented by: Kenny Lin Date: 2013. 2. 1
  2. 2. Agenda Project management: Waterfall VS. Agile Scrum methodology Proposed practice in Moxa IT: open discussion
  3. 3. Traditional project development (a. k. a. Waterfall)
  4. 4. Assumption & philosophy behind waterfall methodology • Plan driven, sequential process • Problems are well defined • Change should be limited (if not forbidden) • Project/product dev. is similar to product manufacturing
  5. 5. What does it mean to be agile (1) • Iterative and incremental development: faster delivery/feedback cycle • Split and prioritize : small batch size
  6. 6. What does it mean to be agile (2) • Favor an adaptive, exploratory approach - just like programming • Collaboration and intense communication • Embrace change
  7. 7. What does it mean to be agile (3) • Early integration • Automated testing & Test Driven
  8. 8. Scrum: the most popular agile methodology
  9. 9. Scrum Basic Concepts • Product Backlog • Sprint • Sprint Backlog • Scrum team
  10. 10. Scrum’s key unit : Sprint • A short-duration, time-boxed iteration • Starts with pre-defined goal • Finishes with ready-for-production increments
  11. 11. Scrum : Sprint based dev. • Fixed length • No goal-altering changes in Sprint
  12. 12. Scrum : Sprint backlog (tasks)
  13. 13. 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
  14. 14. Let’s run it our own way (1) One-month Sprint • Sprint execution • Weekly Scrum • Intense communication with product owner • On-the-spot mentoring (by Kenny) • Continuous integration and testing (SVN)
  15. 15. Let’s run it our own way (1) One-month Sprint • Sprint review • Demo & user (stake holder) feedback • Code review • Process review • “What we have done great, and what we should avoid doing again?”
  16. 16. 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
  17. 17. Thank You Confidential

×