Agile - เว็บไซต์คณะเทคโนโลยี ... · 2018-03-26 · 12...
Transcript of Agile - เว็บไซต์คณะเทคโนโลยี ... · 2018-03-26 · 12...
Agile
KANOKWATT SHIANGJENCOMPUTER SCIENCE
SCHOOL OF INFORMATION AND COMMUNICATION TECHNOLOGY
UNIVERSITY OF PHAYAO
Contents
• Software Development Methodology
• Agile Business Analysis
2
Software Development Methodology
• Agile
• Prototyping
• Spiral
• Incremental
• Waterfall
3http://iansommerville.com/software-engineering-book/web/spiral-model/
https://airbrake.io/blog/sdlc/waterfall-model
Waterfall vs. Agile
4
Analysis
Design
Coding
Testing
Maintenance
24 hours
2-4 weeks
Waterfall
AgileWaterfall
Potentially Shippable Product
increment
Waterfall
• Progress flows downwards
• Projects go through sequentialstages
• Changing requirements affect the deadline
• Very difficult to go back and change something
• Defects found too late
5
Analysis
Design
Coding
Testing
Maintenance
Waterfall
Agile
“Agile is set of values and principles”
• How does a team become Agile?
The make decisions based on the principles and values that the team has decided to follow.
6https://www.youtube.com/watch?v=Z9QbYZh1YXY
Agile
7
• The ability to create and respond to change in order to succeed in an uncertain and fuzzy environment
Agile Manifesto• Individual and interactions over Processes and Tools
• Working Product over Comprehensive Documentation
• Customer Collaboration over Contract Negotiation
• Responding to change over Following a plan
https://www.daxx.com/article/what-does-agile-mean-software-development
Agile Umbrella
8https://th.aliexpress.com/item/New-Style-Free-Shipping-Multicolour-Windproof-Rainbow-Umbrella-Wedding-Party-For-Decoration-Favor/32588346689.html
Agile
Light-weight Approaches
- Lean- Scrum
- Kanban
- Crystal
- XP (Extreme Programming)
Fuller Approaches
- DSDM (Dynamic Systems development method)
- Agile Unified Process
- FDD (Feature Driven Development)
http://agilegod.blogspot.com/2014/01/
12 Principles
• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes control change for the customer’s competitive advantage.
• Delivery working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
9https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/
12 Principles• Business people and developers must work together daily
throughout the project.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within a development team is face-to-faceconversation.
10https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/
12 Principles
• Working software is the primary measure of progress.
• Agile processes promote sustainable development, The sponsors, developers, and users should be able to maintain aconstant pace indefinitely.
• Continuous attention to technical excellence and good designenhances agility (speed)
11https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/
12 Principles
• Simplicity -- the art of maximizing the amount of work not done is essential.
• The best architectures, requirements, and designs emerge fromself-organizing teams.
• At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
12https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/
Agile Business Analysis• Iterative
• Streamlined
• Time-Boxed
• Collaboration
• Releases come early and often
• Communication about the impact of changes
• How to manage the Budget
13https://www.linkedin.com/pulse/what-agile-business-analyst-m-reza-tajeddin-job-seeker-
AgilePlanning- Scrum- Kanban- RAD- Lean
Analysis- Use cases- User story
Design- UX- UML- OOD
Construct- XP- Refactoring
Testing- ATDD - FIT- Automated Testing
Deploy- Integration
Maintenance
14https://www.agilealliance.org/agile101/subway-map-to-agile-practices/
Design
• UX (User eXperience)
• UML
15https://www.lucidchart.com/pages/uml/use-case-diagramhttps://www.uml-diagrams.org/examples/online-shopping-use-case-diagram-example.html
Lean• A systematic method for waste minimization from Toyota
• A set of tools that assist in the identification and steady elimination of waste. As waste is eliminated, quality improves while production time and cost are reduced
• Types of waste• Transport :• Inventory :• Motion :• Waiting :• Over Production :• Over Processing :• Defects :
16
Lean Canvas
17
Problem
Top 3 problems
Solution
Top 3 features
Unique Value Proposition
Single, clear, compelling message that statswhy you are different andworth buying
Unfair Advantage
Can’t be easily copied or bought
Customer Segments
Target customers
Key Metrics
Key activities you measure
Channels
Path to customers
Cost Structure
Customer Acquisition CostsDistribution CostsHostingPeople, etc.
Revenue Streams
Revenue ModelLife Time ValueRevenueGross Margin
Product Market
https://medium.com/@steve_mullen/an-introduction-to-lean-canvas-5c17c469d3e0
12 3
4
5
67
8
9
Photo and video sharing service• Possible Customers List: Anyone that shares lots of photos and
videos.
• More specific:• Photographers• Videographers• Graphic Designers• Architects• Doctors• Parents• Consumers
18https://www.youtube.com/watch?v=7o8uYdUaFR4
Unfair advantages
• Insider information
• Personal authority
• A dream team
• Existing customers
• Large network effects
• Community
• Core values
19
20
Problem
Sharing lots of photos/video istime-consuming
Parent has nofree time
There is lots of demand on thiscontent
Existing AlternativeFacebook, Flickr
Solution
Instant, no-uploadsharing
iPhoto/folder integration
Better notificationtools
Unique Value Proposition
Get back to the moreimportant things in yourlife. Faster.
Share your entire photoand video library in under5 minutes
High-level Concept
Photo and video sharingwithout the uploading
Unfair Advantage
Community
Customer Segments
Parents (customer)Family and friends (viewers)
Early AdoptersParents with young kids
Key Metrics
Key action: Sharingan album/video
Success metric:Build $10 M/year.
Channels
FriendsBirthday partiesAdWordsFacebookWord of Mouth
Cost Structure
Hosting costs - Heroku ( $0)People costs - 40 hrs * $62.5/hr = $10k/month
Revenue Streams
30 days free trial and then $50/year.
https://www.youtube.com/watch?v=7o8uYdUaFR4
Scrum
• Developed by Ken Schwaber and Jeff Sutherland
Definition:
• A framework for developing, delivering and sustaining complex products
21
What is Scrum?
22
https://stackify.com/what-is-scrum-development-vs-rugby/https://hubpages.com/sports/rugby-scrum
Scrum Team
23
Scrum Master Product Owner
Development Team
Product Owner
• Maximizing value of Product and Development Team
• Responsible for managing and ordering the Product Backlog.
• Cancel the sprint
24
Product Owner
Scrum Master
• Promoting and Supporting Scrum
• Helping everyone understand Scrum theory, practices, rules and values
• Facilitating and Coaching the Team
• Team self organize
• Removes obstacles
25
Scrum Master
Development Team
• The professionals who do the work of delivering a releasable increment of
“Done” product at the end of each Sprint.
• Designers, Developers, Testers, etc.
26
Development Team
Scrum Theory
• Empirical Process• Iterative
• Incremental
• Time-boxed
• Collaboration
• 3 Principles• Transparency (task is really meet the definition of done) : open &
honest as a team
• Inspection (check on progress of the sprint goal): 2 weeks
• Adaptation (change the product based on inspection)
27
Scrum Skeleton
24 hours
2-4 weeks
Waterfall
28
Product Backlog Sprint Backlog Sprint
Potentially release shippable product increment
Daily Scrum
Sub tasks
Done
Scrum Artifacts
29
Product Backlog Release Backlog
Estimation
Sprint
Scrum Artifacts• Product Backlog: An that is known
to be (The product owner is responsible)
• Sprint Backlog: selected and delivering the product increment that realizing the
Sprint Goal.
• Product Increment: The completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new increment must be “Done”
30http://www.scrumguides.org/scrum-guide.html
Scrum Events (Time-boxes)• The Sprint (The heart of scrum):
• Sprint Planning: 4 hours meeting for 2 weeks with 2 topics, “ ” and “ ”, then break the story to tasks to commit
• Daily Scrum: Coordination within
• Sprint Review: Make sure that with the team feeding back to the next sprint
• Sprint Retrospective: Meeting to
31http://www.scrumguides.org/scrum-guide.html
Daily Scrum
32
3 Questions for daily scrum
• What did that help the development team?
• What will to help the development team?
• Do I see any me or development team from meeting the Sprint Goal?
33
Retrospectives
34
3 Questions for Retrospective
• What went well during this Sprint?
• What did not go so well during this Sprint?
• What can we do better next time?
35
Burndown Chart• The progress of the team
is tracked using a burndown chart, one of the best project visibility tools, and visual represents a
• The burndown chart provides a
that remains in a given sprint or release.
36https://www.scrumhub.com/scrum-guide/burndowns/
885
Burndown Velocity• The slope of the graph, or
, is calculated by comparing the number of hours worked to the original project estimation and shows the average rate of productivity for each day
37https://www.scrumhub.com/scrum-guide/burndowns/
885
410
Example• You have to finish the Sprint
01 in 885 hours of work within 30 days
• The ideal burndown velocity is / = h/day
• The minimum team member who works 8 h/day is / 8 = 3.7 4 person
38https://www.scrumhub.com/scrum-guide/burndowns/
885
410
Example• After day 19 the work remains
410 hours
• The finished work is 885 - 410 = hours, then the current rate of productivity is / 19
= h/day
• If you want to finish on time in the next 10 days, you have to work / 10 = h/day
• With the current rate you will finish the work in / 25 = 16.4 17 days
39https://www.scrumhub.com/scrum-guide/burndowns/
885
410
Scrum Values
• Commitment :
• Courage :
• Focus :
• Openness :
• Respect :
40http://www.scrumguides.org/scrum-guide.html
3 Questions for daily scrum
• What did that help the development team?
• What will to help the development team?
• Do I see any me or development team from meeting the Sprint Goal?
41
MVP (Minimum Viable Product)
Build
Measure
Learn
42https://www.marketingoops.com/news/tech-update/startups/minimum-viable-product-for-startup/
• โมเดลจ ำลอง หรอื Prototype ทีถ่กูจดัท ำเพือ่ สือ่สำรกบักลุม่เป้ำหมำย ท ำใหผู้ใ้ชแ้ละผูพ้ฒันำ สำมำรถเรยีนรูเ้กีย่วกบั Product ใหไ้ดม้ำกทีส่ดุ
• สมมตฐิำน• ลกูคำ้คอืใคร ?
• ลกูคำ้มคีวำมตอ้งกำร Product ของเรำหรอืไม่?
• วธิแีกปั้ญหำตรงกบัควำมตอ้งกำรของลกูคำ้หรอืไม่?
• ลกูคำ้ยนิดจีำ่ยเงนิเพือ่แลกกบั Product หรอืไม่?
Build
Measure
LearnBuild
Measure
Learn
Kanban (คมับงั)
• A scheduling system for lean manufacturing and just-in-time manufacturing (JIT). Kanban is an Toyota inventory control system for supply chains in 1940s.
• How Kanban works:• Visualize Work
• Limit Work in Process
• Focus on Flow
• Continuous Improvement
43
Kanban
44
BACKLOG NEW IN PROGRESS COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3H
3: USER STORY0 ... 2D
4: USER STORY0 ... 4H
5: USER STORY0 ... 3D
Kanban
45
BACKLOG NEW IN PROGRESS [3] COMPLETE
IN
3: USER STORY0 ... 2D
5: USER STORY0 ... 3D
1: USER STORY0 ... 8H
2: USER STORY0 ... 3H
4: USER STORY0 ... 4H
Work In Progress Limit (WIP Limit)
Kanban
46
BACKLOG NEW IN PROGRESS [3] COMPLETE
IN1: USER STORY
0 ... 8H
2: USER STORY0 ... 3H
3: USER STORY0 ... 2D
4: USER STORY0 ... 4H
5: USER STORY0 ... 3D
Work In Progress Limit (WIP Limit)
Kanban
47
BACKLOG NEW IN PROGRESS [3] COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3H
3: USER STORY0 ... 2D
4: USER STORY0 ... 4H
5: USER STORY0 ... 3D
Work In Progress Limit (WIP Limit)
Kanban
48
BACKLOG NEW IN PROGRESS [3] COMPLETE
IN1: USER STORY
0 ... 8H
2: USER STORY0 ... 3H
3: USER STORY0 ... 2D
4: USER STORY0 ... 4H
5: USER STORY0 ... 3D
Work In Progress Limit (WIP Limit)
Kanban + Scrum
49
BACKLOG SPRINT BACKLOGSPRINT 1
IN PROGRESS [3]COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3D
3: USER STORY0 ... 2D
4: USER STORY0 ... 3D
5: USER STORY0 ... 1W
Kanban + Scrum
50
BACKLOG SPRINT BACKLOGSPRINT 1
IN PROGRESS [3]COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3D
3: USER STORY0 ... 2D
5: USER STORY0 ... 1W
4: USER STORY0 ... 3D
Kanban + Scrum
51
BACKLOG SPRINT BACKLOGSPRINT 1
IN PROGRESS [3]COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3D
3: USER STORY0 ... 2D
5: USER STORY0 ... 1W
4: USER STORY0 ... 3D
Kanban + Scrum
52
BACKLOG SPRINT BACKLOGSPRINT 1
IN PROGRESS [3]COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3D
3: USER STORY0 ... 2D
5: USER STORY0 ... 1W
4: USER STORY0 ... 3D
Kanban + Scrum
53
BACKLOG SPRINT BACKLOGSPRINT 1
IN PROGRESS [3]COMPLETE
IN
1: USER STORY0 ... 8H
2: USER STORY0 ... 3D
3: USER STORY0 ... 2D
5: USER STORY0 ... 1W
4: USER STORY0 ... 3D
Kanban + Scrum
54
BACKLOG SPRINT BACKLOGSPRINT 2
IN PROGRESS [3]COMPLETE
IN
5: USER STORY0 ... 1W
Kanban + Scrum
55
BACKLOG SPRINT BACKLOGSPRINT 2
IN PROGRESS [3]COMPLETE
IN
5: USER STORY0 ... 1W
Kanban + Scrum
56
BACKLOG SPRINT BACKLOGSPRINT 2
IN PROGRESS [3]COMPLETE
IN
5: USER STORY0 ... 1W
Failure Factors
• Fail to See: กำรพลำดทีไ่ม่เห็นโอกำส
• Fail to Move: กำรพลำดทีไ่ม่เร ิม่ท ำในสิง่ทีน่่ำจะตอ้งท ำ
• Fail to Finish: กำรพลำดทีจ่ะท ำบำงอยำ่งใหส้ ำเรจ็ได ้
• Fail More, Fail Faster:
• Learn More, Learn Faster:
• Success More, Success Faster:
57
Q & A
58
References
• Software Engineering, 10th edition, ISBN 978-0-13-394303-0, by Ian Sommerville, published by Pearson Education 2016
• Intro to Scrum in Under 10 Minutes (https://www.youtube.com/watch?v=XU0llRltyFM)
• http://www.scrumguides.org/scrum-guide.html
• https://www.scrumhub.com/scrum-guide/
• https://www.axosoft.com/
• https://www.youtube.com/watch?v=ACcfYB_5iV8&list=PLebXUHgaZIX59v5YBgxRYCV7batgaCN2G
59