The document summarizes a guest lecture on agile development given by Edison Wong. It defines agile development and describes popular agile methods like Scrum and Kanban. It compares Scrum and Kanban and outlines why agile development is preferable to traditional waterfall methods. The lecture also included a 15 minute tutorial on using JIRA for agile projects and covered advanced topics like branching strategies, code reviews, and continuous integration.

1. CUHK CSCI 4140 2015 Spring
Guest Lecture
Agile Development
Edison Wong
2015 Mar 2nd

2. Wong Hoi Sing, Edison
● CEO, Founder, PantaRei Design
– 2009, PantaRei Design founded
– 2010, HKFYG YBHK applicant
– 2011, ITF SERAP applicant
– 2011, HKSTP Incu-Tech applicant
● FOSS and Drupal Developer, Contributor and HKDUG Co-founder
– 2000, Debian GNU/Linux 2.2 ('potato')
– 2005, Drupal Developer
– 2008, BarCamp HK Speaker
– 2008, HKDUG Co-founder
– 2011, Drupal 7.x Core Contributor
● http://hswong3i.net
● hswong3i@pantarei-design.com

3. PantaRei Design
●
Everything Changes and Nothing Remains Still
●
Reinvent Enterprise with Open Source Software and Cloud Computing
●
Hong Kong based FOSS service provider
– Content Management System (CMS) with Drupal
– Cloud Hosting Solution with Amazon Web Services (AWS)
– Team collaborate solution with Atlassian
●
Business Partner with industry leaders
– 2012, AWS Consulting Partner
– 2013, Acquia Partner
– 2013, Atlassian Experts
– 2014, Rackspace Hosting Partner

4. PantaRei Design (cont.)
● History
– 2010
● Founded by Edison Wong
● Applicant of The Hong Kong Federation of Youth Groups (HKFYG) Youth
Business Hong Kong (YBHK) Programme
– 2011
● Applicant of Innovation and Technology Fund (ITF) Small Entrepreneur
Research Assistance Programme (SERAP)
● Applicant of Hong Kong Science & Technology Parks (HKSTP) Incu-Tech
Programme
– 2014
● Graduate as HKSTP Talent

11. Outline
●
What is Agile Development?
●
Why Agile Development?
●
15 mins Tutorial
●
Advanced Topic(s)

12. What is Agile Development?
●
Agile
●
Scrum
●
Kanban
●
Scrum vs Kanban

13. Agile
●
A group of software development methods
●
Requirements and solutions evolve through
collaboration between self-organizing, cross-
functional teams
●
Promotes adaptive planning, evolutionary
development, early delivery, continuous
improvement, and encourages rapid and flexible
response to change

15. Scrum
●
Iterative and incremental
●
Fixed-length iterations (e.g. 2~4 weeks)
●
4 Ceremonies
– Sprint planning
– Daily stand-up
– Sprint demo
– Sprint retrospective

18. Scrum (cont.)
●
Roles
– Product Owner
– Development Team
– Scrum Master

19. Scrum (cont.)
●
User stories
– Express customer need as a story
– Set user role
– Small amount of work
– Should include notes for needed

22. Scrum (cont.)
●
Task
– For developer
– Get engineer talking with product owner
– Get mutual understanding of the story
– Satift customer needs

24. Scrum (cont.)
●
Burndown chart
– Public displayed chart showing remaing work in
the sprint backlog
– Simple view of the sprint progress
– Quick visualization for reference

27. Kanban
●
Just-in-time delivery
●
Only focused on work that's actively in
progress
●
Keep pluck the next work item off the top of
the backlog
●
Keep the most important work items on the
top of the backlog

32. Scrum vs Kanban
Scrum Kanban
Cadence Regular fixed length sprints
(ie, 2 weeks)
Continuous flow
Release methodology At the end of each sprint if
approved by the product
owner
Continuous delivery or at the
team's discretion
Roles Product owner, scrum
master, development team
No existing roles. Some
teams enlist the help of an
agile coach.
Key metrics Velocity Cycle time
Change philosophy Teams should strive to not
make changes to the sprint
forecast during the sprint.
Doing so compromises
learnings around estimation.
Change can happen at any
time

33. Why Agile Development?
●
Waterfall
●
Agile vs Waterfall

34. Waterfall
●
Usually sucks
●
Planning far in advance
●
Lack of visibility into rate of progress
●
Project fall behind schedule (easily)

36. Agile vs Waterfall
Agile Waterfall
Planning scale Short Long
Distance with customer Short Very long
Time to discover problem Short Very long
Ability to respond quickly
to change request
Short N/A

37. 15 mins Tutorial
●
Atlassian JIRA Agile
– Scrum
– Kanban

38. Advanced Topic(s)
●
Branching Strategies
●
Code Reviews
●
Continuous Integration (CI)

39. Branching Strategies
●
Three branching strategies for agile teams
– Release branching
– Feature branching
– Task branching
●
Usually handling by GIT
– Github
– Atlassian Stash
●
Validate, validate, validate

40. Code Reviews
●
So, what exactly is a code review?
– When a developer is finished working on an issue, another
developer looks over the code and considers questions
●
Code reviews share knowledge
●
Code reviews make for better estimates
●
Code reviews enable time off
●
Code reviews mentor newer engineers
●
But code reviews take time!

43. Continuous Integration (CI)
●
Merging all develop working copies with a
share mainline several times a day
●
Protect quality in the code base
– Continuous builds
– Test automation (e.g. phpunit)
●
Branching and CI: a match made in Heaven!

46. Q&A

47. References
●
http://en.wikipedia.org/wiki/Agile_software
_development
●
http://en.wikipedia.org/wiki/Scrum_%28sof
tware_development%29
●
http://en.wikipedia.org/wiki/Kanban_%28d
evelopment%29
●
https://www.atlassian.com/agile

48. Thank You
●
Please feel free to contact us:
– PantaRei Design Limited
– Unit 326, 3/F, Building 16W
No.16 Science Park West Avenue
Hong Kong Science Park, Shatin, N.T.
– Phone: +852 2576 3812
– Fax: +852 3753 3663
– Email: sales@pantarei-design.com
– Web: http://pantarei-design.com