-
Notifications
You must be signed in to change notification settings - Fork 0
/
Agile+Jira.txt
169 lines (116 loc) · 5 KB
/
Agile+Jira.txt
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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
AGILE:
*Agile is an approach to software development under which requiremnets and solutions evolve through the collaborative effort of self-organizing and cross - functional teams and their customer/end user.
*Both development and testing activities are concurrent unlike the waterfall model.
AGILE TEAM: It is a collection of multiple like testers ,developers,product manager,etc.. will be the part.
* In this , the role is not important the task is important like no seniors and juniors everybody will fall under the same.
* In agile process developing and testing goes parallel.
*Whenever a client need to change any requirments , we can esaily accommodate those requirements.
TERMINOLOGIES[EPIC,STORY,TASK]:
FUNCTIONAL REQUIREMENTS DOCUMENT: which contains the requirements which are specified by the customer.
*In the agile process documentation required will be avoided 90%.
*The epic and stories are derived by product owner/scrum master.
EPIC: epic is a large requirement define the business needs[ONLINE BANKING]
STORY: It is a smaller requirement [LOGIN,TRANSFER MONEY, CHECK BALANCE]
TASK:
Review the story
Estinate the story
Desugn
Code
Unit Testing
Intefration Testing
etc..
QA:
Review the story
Test Cases
Test Scenarios
Test data
Reviews
Test Environment
Report Bugs
etc..
AGILE ROLES:
PRODUCT OWNER: he is aperson responsible for getting the requirements from the customer.
*define the features of the product
*decide on release date and content
*prioritize features according to market value
*adjust features and priority every iteration ,as needed
*accept or rejecr work results.
SCRUM MASTER: who is factilitator the complete agile process.
*Enable close cooperation across all roles and functions.
SCRUM TEAM: developers and testers should work together to get the deliver.
DOR(DEFINATION OF READY):
*user story is clear.
*user story is testable
*user story is feasible
*user story defined
*user story acceptance criteria defined
*user story dependencies identified
*user story sized by development team
*scrum team accepts user experience artefacts.
*performance criteria identifed ,where appropriate
*scalability criteria identified ,where approprite
*security criteria identified, where appropriate
*person who will accept the story is identified
*Team has a good idea what it will mean to demo the user story.
DOD(DEFINATION OF DONE):
*code produced(all to doitems in code completed)
*code commented ,checked inand run against current version in source
*Relevant documentation.diagrams produced and / or updated.
PRODUCT BACKLOG: It is prepared by prodct owner and which contains the requiremnets.[contains complete stories]
SPRINT/ITERATION: time interval to complete a task one version of software.
SPRINT BACKLOG: contains the commited storys
STEPS:
1.product owner: cerate baclog
*sprint:Time interval
*Story Point: developers and QA give estimation for the specific story.
* Estimation gives in the fibonaccci series
2.Meeting
3.Sprint Backlog: sprint interval, evaryday scrum meeting[15min]
4.finished work[sprint review, sprint retrospective]
ADVANTAGES OF AGILE SCRUM:
*we can save time and cost of the project.
*the quality can be ensured because each and every sprint will be tested multiple times.
*The requirements change can be accepted at any level of the project maintenanace.
*All the participating in scrum meting so that transparency can be maintained.
*Each and every sprint we are delivering to the client so we can maintain the customer satisfaction and we can avoid deliveryrisk of the project.
----------------------JIRA TOOL---------------------------------
Managing agile process
*create backlogs
*create sprints
*tasks
* update story status scrum board
write test cases
Execute test cases update of the test cases
AGILE SCRUM ACTIVITIES:
1.How to install and configure JIRA Tool
2.How to create project in Jira
sigin > create new project > select template [scrum] > create
3.How to add users/people in Jira
Jira setting > invite user
[backlog are created while doing the projects]
4.How to create User stories in Jira
Baclog page > create > by default story is selected > add summary feature/title > add issue > create.
[update the sprint points in every story]
5.Creating sprint in Jira
Backlog page > create sprint
6.Adding user stories to sprint
Backlog > drag and drop story into Sprint.
7.starting sprint
Backlog > start sprint
8.adding sub tasks to story
Board > click story > add child issuse.
9.sprint life cycle in Jira
10.creating bugs in Jira
TEST MANAGEMENT ACTIVITIES:
Pre -requisites:
1)Dashboard > apps > explore > search > Zephyr > try
2)Adding issue type > project settings > Issue types > add new issuse > type "test".
1.How to create test cases in Jira with Zephyr plugin
2.creating Test cycles
3.Executr/update test cases in Jira
ISSUES TYPES IN JIRA:
Epic
story
task
bug
task