-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathAgile
80 lines (59 loc) · 1.52 KB
/
Agile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
Ajile lifecycle
Envision -What are we trying to build
Project Charter
Team Collabaration tools
Team Norms
(1 time)
Speculate
Feature baseid deliver plan
Explore
Stand up meetings
Develope project
Adapt
Pause and reflect
Review features
Reflect on team preformance
Close
Deliverables are complete
Final leesons captured
.......Envision...........
Project Charter
Product Vision (summary statement)
Target customer
Key benefits
Purpose of the project
Poject Sponcer
Project Manager
Team Collaboration Tools
Track and report status
Facilitate joint feature development
Push information out to team members
Everyone works together on the project
How will we work together?
Common Risk
Overy ambition scheule
Not enough dcision maker on team
End of Envison pahse
Project Charter
Collaboration tools
Low risk team in place
Scope, boundaries,
Product Backlog
Iterations
SCRUM - Sprints - bit by bit improved over time
Product owner speaks customers languag
-product owner prioritizes the work
-creates user roles
User Rolse - bunlde of user experiences
-Visitor, Customer, Customer Premium
User Stories
-A conversation
-A short story from the user's perspective about what they find valuable in the product
-As a ,user role., I <want/need/can/ect> <goal> so that <reason>
-uses users language not tech language
-linked to business value
-Card, Conversation, confirmation
-put it on an index card
-User stories are about creating group conversations
-Acceptance Criteria, Back of card, matches user story
-when will it be acomplished