Workshop by Jira and Scrum Ramazan Karami @ ModernPal @merichle

1. Ramazan Karami
iOS Developer @ ModernPal
www.linkedin.com/in/merichle

2. ‫عناوین‬:
❖‫اجمالی‬ ‫معرفی‬‫اسکرام‬‫سازی‬ ‫پیاده‬ ‫نحوه‬ ‫و‬
❖‫ار‬‫ز‬‫اف‬ ‫نرم‬ ‫از‬ ‫ارش‬‫ز‬‫گ‬ ‫دریافت‬‫جیرا‬‫اطلاعات‬ ‫بررسی‬ ‫و‬

4. ‫هست؟‬ ‫چی‬ ‫اسکرام‬
‫رو‬ ‫اگبی‬‫ر‬ ‫بازی‬ ‫تو‬ ‫دوباره‬ ‫شروع‬‫اسکرام‬‫میگن‬...

5. ‫هست؟‬ ‫چی‬ ‫اسکرام‬
‫بصورت‬ ‫ار‬‫ز‬‫اف‬‫نرم‬ ‫ی‬‫توسعه‬ ‫سیستم‬ ‫از‬ ‫ای‬‫شاخه‬‫چابک‬(Agile... )
‫جلوئه‬ ‫به‬ ‫رو‬ ‫و‬ ‫مکرر‬ ‫ایند‬‫ر‬‫ف‬...

6. ‫هست؟‬ ‫چی‬ ‫اسکرام‬
‫جلسه‬‫روزانه‬‫در‬‫کاری‬ ‫ساعت‬ ‫اولین‬
❖‫اره‬‫ر‬‫ق‬ ‫که‬ ‫کارهایی‬‫امروز‬‫بدیم‬ ‫انجام‬...
❖‫که‬ ‫کارهایی‬‫دیروز‬‫دادیم‬ ‫انجام‬...

7. ‫هست؟‬ ‫چی‬ ‫اسکرام‬
❖‫انه؟‬‫ز‬‫رو‬ ‫ا‬‫ر‬‫چ‬ ‫خب‬
❖‫بررسی‬‫گاه‬‫ناخودا‬‫انه‬‫ز‬‫رو‬ ‫های‬ ‫فعالیت‬...

8. ‫هست؟‬ ‫چی‬ ‫اسکرام‬

10. ‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:
‫اول‬ ‫مرحله‬:
‫تهیه‬Backlog‫محصول‬
‫مرحله‬ ‫این‬ ‫تو‬‫نیازهای‬ ‫تمامی‬‫اساس‬ ‫بر‬ ‫کارفرما‬‫اهمیت‬ ‫درجه‬‫میشه‬ ‫مشخص‬...

11. ‫دوم‬ ‫مرحله‬:
‫بندی‬ ‫فاز‬
❖‫اصلی‬ ‫فاز‬ ‫چند‬ ‫به‬ ‫کار‬ ‫کل‬ ‫تقسیم‬
‫بصورت‬ ‫پروژه‬ ‫تحویل‬‫فاز‬ ‫به‬ ‫فاز‬
(‫چابکه‬ ‫سیستم‬ ‫تعاریف‬ ‫از‬ ‫یکی‬ ‫این‬:Early Delivery)
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

12. ‫سوم‬ ‫ی‬‫مرحله‬:
‫اسپرینت‬ ‫ریزی‬‫برنامه‬ ‫ی‬‫جلسه‬
❖‫چه‬‫اهدافی‬‫داریم؟‬ ‫اسپرینت‬ ‫این‬ ‫در‬
❖‫چطور‬‫برسیم؟‬ ‫اهداف‬ ‫این‬ ‫به‬
❖‫حضور‬‫تیم‬ ‫اعضای‬ ‫تمامی‬‫باشد‬‫می‬ ‫امی‬‫ز‬‫ال‬.
❖‫بندی‬ ‫زمان‬‫شود‬ ‫انجام‬ ‫لاگ‬‫بک‬ ‫در‬ ‫موجود‬ ‫های‬‫تسک‬(‫از‬ ‫بیشتر‬ ‫نباید‬8‫شود‬ ‫ساعت‬.)
‫ای‬‫ز‬‫ا‬ ‫به‬‫هفته‬ ‫هر‬‫اسپرینت‬‫جلسه‬ ‫ساعت‬ ‫دو‬‫می‬ ‫ار‬‫ز‬‫برگ‬ ‫اسپرینت‬‫شود‬
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

13. ‫چهارم‬ ‫ی‬‫مرحله‬:
‫اسپرینت‬ ‫سند‬ ‫ی‬‫تهیه‬
o‫ا‬‫ر‬‫اج‬ ‫ی‬‫نحوه‬،‫ات‬‫ر‬‫نف‬ ‫تعیین‬‫و‬‫بندی‬‫زمان‬‫با‬ ‫متمرکزه‬ ‫کارها‬‫کامل‬ ‫دیتیل‬‫مش‬‫شود‬‫می‬ ‫خص‬.
o‫اسپرینت‬ ‫یک‬ ‫ان‬‫و‬‫عن‬ ‫به‬ ‫رو‬ ‫فاز‬ ‫هر‬...
‫یا‬
o‫اسپرینت‬ ‫چند‬ ‫به‬ ‫فاز‬ ‫یک‬...
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

14. ‫چهارم‬ ‫ی‬‫مرحله‬:
‫اسپرینت‬ ‫سند‬ ‫ی‬‫تهیه‬
‫تهیه‬‫اسکرام‬ ‫تخته‬(Scrum Board:)
❖‫انجام‬ ‫صف‬ ‫در‬(To-Do)
❖‫انجام‬ ‫حال‬ ‫در‬(Doing)
❖‫شده‬ ‫انجام‬(Done)
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

15. ‫پنجم‬ ‫ی‬‫مرحله‬:
‫اسکرام‬ ‫اجرای‬
‫های‬ ‫فعالیت‬ ‫به‬ ‫باتوجه‬ ‫ام‬‫ر‬‫اسک‬ ‫بورد‬ ‫سازی‬ ‫مرتب‬‫دیروز‬‫و‬‫امروز‬
o‫فقط‬‫ان‬‫و‬‫عن‬‫میشود‬ ‫بیان‬ ‫ها‬ ‫فعالیت‬
o‫همه‬‫ایستاده‬‫باشن‬
o‫جملات‬ ‫مخاطب‬‫تیمی‬‫هم‬‫اسک‬ ‫مسئول‬ ‫یا‬ ‫فنی‬ ‫مدیر‬ ‫فقط‬ ‫نه‬ ‫باشد‬ ‫تیم‬ ‫اعضای‬‫ام‬‫ر‬
o‫جلسات‬‫جدی‬‫حقایق‬ ‫کتمان‬ ‫از‬ ‫دور‬‫به‬ ‫و‬
o‫از‬ ‫بیشتر‬ ‫جلسه‬15‫دقیقه‬‫نکشه‬ ‫طول‬
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

16. ‫ششم‬ ‫ی‬‫مرحله‬:
‫اسپرینت‬ ‫تحویل‬
‫اص‬ ‫رو‬ ‫کار‬ ‫این‬ ،‫میدیم‬ ‫تحویل‬ ‫رو‬ ‫پروژه‬ ‫از‬ ‫فاز‬ ‫یک‬ ‫یا‬ ‫فاز‬ ‫از‬ ‫بخشی‬ ‫مرحله‬ ‫این‬ ‫در‬ً‫ا‬‫طلاح‬
‫پروژه‬ ‫فازی‬ ‫و‬ ‫ایشی‬‫ز‬‫اف‬ ‫تحویل‬‫نامیم‬‫می‬.
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

17. ‫هفتم‬ ‫ی‬‫مرحله‬:
‫اسپرینت‬ ‫بررسی‬
o‫کارهایی‬ ‫چه‬‫شده‬ ‫انجام‬‫کارهای‬ ‫چه‬ ‫و‬‫مونده‬ ‫ناقص‬‫؟‬
o‫ارش‬‫ز‬‫گ‬‫اسپرینت‬
o‫اسپرینته‬ ‫ریزی‬‫برنامه‬ ‫ی‬‫جلسه‬ ‫نصف‬ ً‫ا‬‫معمول‬ ‫جلسه‬ ‫این‬ ‫زمان‬...
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

18. ‫هشتم‬ ‫ی‬‫مرحله‬:
‫اسپرینت‬ ‫بازنگری‬
o‫ضعف‬ ‫نقاط‬ ‫رفع‬
o‫قوت‬ ‫نقاط‬ ‫بهبود‬
o‫یندها‬‫ا‬‫ر‬‫ف‬ ،‫ارتباطات‬ ،‫اد‬‫ر‬‫اف‬ ‫عملکرد‬ ‫بهبود‬ ‫مورد‬ ‫در‬ ‫گیری‬‫تصمیم‬
o‫نیاز‬ ‫مورد‬ ‫ارهای‬‫ز‬‫اب‬ ‫ی‬‫توسعه‬
o‫اسپرینت‬ ‫یک‬ ‫ای‬‫ر‬‫ب‬ ً‫ا‬‫معمول‬ ‫و‬ ‫بررسیه‬ ‫ی‬‫جلسه‬ ‫از‬ ‫کمتر‬ ‫هم‬ ‫جلسه‬ ‫این‬ ‫زمان‬۲‫ای‬‫هفته‬۳‫میشه‬ ‫گذاشته‬ ‫وقت‬ ‫ساعت‬.
‫اسکرام‬ ‫اصلی‬ ‫مرحله‬ ‫هشت‬:

20. Burndown Chart
A Burndown Chart shows the actual and estimated amount of work to be done in a sprint. The horizontal x-axis in a Burndown Chart indicates time, and the vertical y-axis indicates cards
(issues).
Use a Burndown Chart to track the total work remaining, and to project the likelihood of achieving the sprint goal. By tracking the remaining work throughout the iteration, a team can
manage its progress, and respond to trends accordingly. For example, if the Burndown Chart shows that the team may not likely reach the sprint goal, then the team can take the necessary
actions to stay on track.
Before you begin
● The Burndown Chart only applies to Scrum boards.
● Story Points on subtasks are not included in the Burndown Chart. (Only Story Points on parent tasks).dedulcni era
Viewing the Burndown Chart
1. Click Jira home > Projects tcejorp tnaveler eht tceles neht >.
2. Click Reports tceles neht ,Burndown Chart .
● To choose a different sprint, click the sprint drop-down.
● To choose a different estimate statistic, click the estimation statistic drop-down. This change will be saved for you, for when you next visit this chart.
Tip: Click How to read this chart troper eht fo noitpircsed trohs a weiv ot troper eht fo pot eht ta.

21. Burndown Chart

22. Sprint Report
The Sprint Report shows the list of issues in each sprint. It is useful for your Sprint Retrospective meetings, and also for mid-sprint progress checks.
Tip: If you have
Jira Software
connected to Confluence, you can create a 'Retrospectives' page via the Linked pages eeS .kniltnirps a ot egap ecneuflnoC a gnikniLsliated rof.
Before you begin
● This page only applies to Scrum boards.
● Estimates on sub-tasks are not included in the Sprint Report. (Only estimates on parent issues).dedulcni era
Viewing the Sprint Report
1. Click your Jira icon)(
2. Click Projectstcejorp tnaveler eht tceles neht
3. Click Reports tceles neht Sprint Report
4. Select the relevant sprint from the sprint drop-down
Tip: Click How to read this chart troper eht fo noitpircsed trohs a weiv ot troper eht fo pot eht ta.

23. Sprint Report

24. Control Chart
The Control Chart shows the Cycle Time (or Lead Time) for your product, version, or sprint. It takes the time spent by each issue in a particular status (or statuses), and maps it
over a specified period of time. The average, rolling average, and standard deviation for this data are shown.
A Control Chart helps you identify whether data from the current sprint can be used to determine future performance. The less variance in the cycle time of an issue, the higher the
confidence in using the mean (or median) as an indication of future performance.
Here are some of the ways that you could use a Control Chart:
● Analyze your team's past performance in a retrospective,
● Measure the effect of a process change on your team's productivity,
● Provide external stakeholders with visibility of your team's performance, and
● For Kanban, use past performance to set targets for your team.
Viewing the Control Chart
1. Click your Jira icon)(
2.
3. Click Projectstcejorp tnaveler eht tceles neht
4. Click Reports tceles neht ,Control Chart
5. Configure the chart as desired. The screenshot at the top of this page highlights the controls that you can use to configure the Control Chart
Tip: Click How to read this chart troper eht fo noitpircsed trohs a weiv ot troper eht fo pot eht ta.

25. Control Chart
1. Issue details: Select a dot to see data for a specific issue.
2. Zoom in: doirep emit cfiiceps a no sucof ot trahc eht fo aera na thgilhgiH.
3. Time scale: Configure the time period you want data for.
4. Refine report: Select the columns, filters, and swimlanes you want data for.

26. Release Burndown
The Release Burndown report shows you how your team is progressing against the work for a release. In
Jira Software
,there is no 'release' entity —a version is equivalent to a release (hence, the term 'version' will be used instead of 'release' in this document). The report will show data based
on the estimation statistic that your board is using.
Here are some of the ways that you could use a Release Burndown report:
● See how quickly your team is working through the backlog,
● See how work added and removed during the sprint has affected your team's overall progress, and
● Predict how many sprints it will take to complete the work for a version, based on past sprints and changes during the sprints.
If you have used the Version Report before, you will notice some similarities. However, the Release Burndown report is optimized for scrum teams that work in sprints —
which makes tracking much easier.
Viewing the Release Burndown report
1. Click your Jira icon)(
2. Click Projectstcejorp tnaveler eht tceles neht
3. Click Reports tceles neht Release Burndown
4. Select the relevant version from the Release Burndown drop-down. You will be able to choose from versions that are in projects configured for your board (via the
board's filter)
Tip: Click How to read this chart troper eht fo noitpircsed trohs a weiv ot troper eht fo pot eht ta.

27. Release Burndown

28. Velocity Chart
The Velocity Chart shows the amount of value delivered in each sprint, enabling you to predict the amount of work the team can get done in future sprints. It is useful during
your sprint planning meetings, to help you decide how much work you can feasibly commit to.
Viewing the Velocity Chart
1. Click your Jira icon)(
2. Click Projectstcejorp tnaveler eht tceles neht
3. Click Reports tceles neht Velocity Chart
4. The Velocity Chart will be displayed, showing your last seven completed sprints
Tip: Click How to read this chart troper eht fo noitpircsed trohs a weiv ot troper eht fo pot eht ta.

29. Velocity Chart
1. Estimation statistic: y ehT-setamitsE .stniop yrots gnisu si maet eht ,evoba elpmaxe eht nI .seirots gnitamitse rof desu citsitats eht syalpsid sixassenisub no desab eb osla nac
eeS .eciohc ruoy fo dlefi ciremun yna ro ,tnuoc eussi ,sruoh ,eulavgnikcart dna noitamitse gnirugfinoCofni erom rof.
2. Commitment: etrats sah tnirps eht retfA .snigeb ti nehw tnirps eht ni seussi lla fo etamitse latot eht swohs tnirps hcae rof rab yarg ehT,dyna ro ,tnirps eht ot dedda seirots yna
latot siht ni dedulcni eb ton lliw ,setamitse ot edam segnahc.
3. Completed: The green bar in each sprint shows the total completed estimates when the sprint ends. Any scope changes made after the sprint started are included in this total.
4. Sprints: x ehT-tsal eht syalpsid sixa7 sprints completed by the team. This data is used to calculate velocity .
Other things to note about the Velocity Chart:
● It's board-specific, which means it'll only include issues that match your board's saved filter.
● It's based on your board's column mapping. An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an
issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information.

30. Version Report
The Version Report shows your team's progress towards the completion of a version. The Version Report also shows you the predicted Release Date, based on your team's
average rate of progress (velocity) since the start of the version, and the estimated amount of work remaining.
Before you begin
● This page only applies to Scrum boards.
Viewing the Version Report
1. Click your Jira icon)(
2. Click Projectstcejorp tnaveler eht tceles neht
3. Click Reports tceles neht ,Version Report
4. Select the relevant version from the Version Report drop-down
Tip: Click How to read this chart troper eht fo noitpircsed trohs a weiv ot troper eht fo pot eht ta.

31. Version Report

32. Version Report
Before you start using the Version Report, you should get to know how it works. The following information will help you understand the key functionalities of the Version Report:
● The Version Report is board-specific –that is, it will only include issues that match your board's saved filter.
● The Version Report will exclude issues of a 'sub-task type '.
● The Version Report shows 'Released' versions but not 'Archived' versions. For more about version status, see Managing versions(
● Jira admin
● documentation.)
● The Version Report is based on your board's column mapping. An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your
board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more
information.
● The horizontal axis starts on the version's Start Date; or if no Start Date is specified, the date on which an issue was first added to the version. The graph shows the state your
version was in at any given point in time, in terms of your total and completed Story Points (or other Estimation Statistic of your choice), so that you can see how the scope may
have changed, and how you are progressing towards completion of the estimated work.
● The graph shows you the following predictions:
● the Predicted Release Date )enil eulb(– that is, the date at which you can expect all issues in your version to be complete, based on your average daily velocity and the
amount of estimated work remaining.
● the Predicted Release Date (Optimistic) )enil eulb eht fo tfel eht ot aera dedahs(– that is, the earliest date by which you might expect the version to be complete. (The
'optimistic' date is calculated by adding 10% to the average daily velocity.)
● the Predicted Release Date (Pessimistic) )enil eulb eht fo thgir eht ot aera dedahs(– that is, the latest date by which you might expect the version to be complete. (The
'pessimistic' date is calculated by subtracting 10% from the average daily velocity.)
● 10% of the estimated work for the version will need to be complete before the predictions can be calculated.

33. Become a Pal