Foundation of agile frameworks and how to work with them.

1. Working with Agile
Development
Brian Hsieh
@briankhsieh

2. Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

3. What does it mean?
Ability to respond to customers quickly.
Rapidly delivering working products and quickly getting feedback.
MVP: You decide what’s minimum, customer decides what’s viable.
http://www.thestartupway.com/

4. How?

5. Scrum v.s. Kanban
Fixed-time.
You know when you will get something.
You can have an idea what you will get.
You can change the scope anytime, kind of.
Fixed-scope.
You know what you will get when it’s done.
You have an idea when you will get it.
You can change the scope any time, kind of.
scrum kanban

6. Scrum v.s. Kanban- Project Timeline
scrum kanban
intake
deliver
queue
intake
deliver
queue
Lead Time
Cycle Time
Sprints
Backlog

7. Kanban
You might be doing it everyday. :)
Make sure the team is working on the most important items.
Limit work-in-progress(WIP).
Optimize cycle time. TO DO
DOING
DONE
“When everything is a priority, nothing is a priority.”
― Karen Martin, The Outstanding Organization: Generate Business Results by Eliminating Chaos and
Building the Foundation for Everyday Excellence
“Multitasking is a lie.”
― Gary Keller, The One Thing: The Surprisingly Simple
Truth Behind Extraordinary Results

8. Scrum
Sprint planning Backlog refinement
Backlog estimation Definition-of-done
Retrospectives Standups
Burndown & velocity chart Sprint review
Scrum of scrum
Consistent velocity.
Minimize interruption.
Continuous improvement.

9. Why so Many Ceremonies?
A tangible way to explain and manage uncertainty with transparency.
Plans are worthless, but planning is essential.
~~~ Dwight D. Eisenhower

10. Plan

11. The Idea
I can run 5 miles per hour.
The distance from my house to the office is around 10 miles.
I should be able to run to the office in 2 hours!! ( 20/5 )
I can definitely run to the office in 3 hours!!!!
velocity
backlog estimation
forecasting
commitment

12. The Concept of Estimation
1 2 3 5 8 13 21 !!!!!!
Small Large
Egg fried riceSteam rice Rice pudding Briyani
Seafood paella?
What’s the unit????
Story points, size chart.
Person-hours, person-days, person-weeks.
My personal opinion, be consistent and use whatever makes sense to your team.

13. Plan!!!
Velocity 10
Feature A 2
Feature B 5
Feature C 3
Feature D 8
Feature E 2
Feature F 4
Feature G 3
Feature H 1
Feature I 2
Feature J 13
Feature K 2
Feature L 2
Feature M 2
More certain
Fuzzy
Sprint 1
Sprint 2
Sprint 3
Sprint 4
Sprint 5+
Checking dependency
Sprint planning Backlog refinement Backlog estimation

14. How about
kanban?
Cycle time seems useless when the features are
different sizes!!
You can still gauge.
Say average cycle time is 5 days.
Feature A 2
Feature B 5
Feature C 3
Feature D 8
Feature E 2
Feature F 4
Feature G 3
Feature H 1
Feature I 2
Feature J 13
Feature K 2
Feature L 2
Feature M 2
One Month

15. Execute

16. No interruptions, please!!!
The team really can use some uninterrupted time during the execution phase.
NO scope changes until cycle is finished, sprint in scrum, a feature in kanban.
NO bothering the team with unnecessary meetings and status reports.
Maker’s schedule. Manager’s schedule.

17. How do I know what’s going on?
??????????????????????????????
Scrum teams usually have a daily standup. Make an effort to join.
Kaban team should have similar standup activities, not necessaries daily.
Burndown chart.

18. When can I ask for new features?
scrum kanban
intake
deliver
queue
intake
deliver
queue

19. Feedback

20. Feedback on the outcome, the deliverables, the working product.
Feedback for the process, the team’s execution, anything.
Sprint review/Feature review
Retrospectives
“Insanity is doing the same
thing, over and over again, but
expecting different results.”

21. Program Management in
Agile World?!

22. Roles
Team
Product owner
Scrum master
Team
Product owner (maybe)
Kanban master (maybe)
scrum kanban
executor
owner
facilitator
Engineering manager
Team leader
Project manager
Program manager
Product manager
Engineering manager
Project manager
Program manager

23. Who and how and when?
Dependencies?
Roadmap?
Report?
PRD?
Architecture review?
Launch plan?
Gatekeepers?
You can go on and on and on...

24. Program Management in Agile
Aligning project execution and company strategy.
Different principles, different mechanisms, but the role is the same.
Although……………...

25. Stakeholders
Stakeholder management could be challenging.
For example, if you have a weekly executive review meeting, but you have 2 week
sprints scrum team!!!!
Gatekeeper!

26. Agile at Scale
Ensure supports across agile and non-agile teams.
Program managers are the key to glue different verticals and different best
practices.
The principles is the key, not the process.
Funding value stream rather than the projects.
Be adaptive.
https://hbr.org/2018/05/agile-at-scale
“Everything is an experiment.”
― Tibor Kalman

27. Thank you!