-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
150 lines (122 loc) · 5.85 KB
/
index.html
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
<!doctype html>
<html lang="en">
<head>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-49591534-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-49591534-1');
</script>
<meta charset="utf-8">
<title>Cardnator - Break down cards to deliver value faster</title>
<meta name="description" content="Cardnator - Break down cards to deliver value faster">
<meta name="author" content="Beatriz Sena, Felipe Chagas, Nayara Mariotti, Ceci Fernandes">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<!-- font imports -->
<link href='http://fonts.googleapis.com/css?family=Dancing+Script' rel='stylesheet' type='text/css'>
<link href='http://fonts.googleapis.com/css?family=Londrina+Sketch' rel='stylesheet' type='text/css'>
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/nu.css" id="theme">
<link rel="stylesheet" href="css/talk.css">
<!-- If the query includes 'print-pdf', use the PDF print sheet -->
<script>
document.write( '<link rel="stylesheet" href="css/print/' + ( window.location.search.match( /print-pdf/gi ) ? 'pdf' : 'paper' ) + '.css" type="text/css" media="print">' );
</script>
</head>
<body>
<div class="reveal linear center">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<section class="question">
<h4>Ask yourself...</h4>
<h2>Can we borrow any technical debts for leverage, and pay it later?</h2>
</section>
<section class="explanation">
<h2>Are there <a target="_blank" href="https://www.pipartners.com/technical-debt/">technical debts</a> you can use as leverage for earlier delivery, and pay later?</h2>
<h3>Why does it matters</h3>
</br>
<p>Ignoring technical debt leads to long-term disadvantages that put the business – and value creation plans – at risk.</p>
<h3>What to do</h3>
<p>When technical debts are identified, it is important to classify and document them. We suggest the classification of debts according to the following classifications:</p>
<ol>
<li>Makes the activity unfeasible?</li>
<li>It brings operational risk to the business?</li>
<li>It happens with a certain frequency, but it is mapped?</li>
<li>It can happen, but we have no previous evidence?</li>
</ol>
<p>We suggest that the items classified 1 and 2 be evaluated with greater criteria and have the risks mitigated and/or the task replanned. The items 3 and 4, have the green light to move forward, but always remember to document them.</p>
</section>
</section>
<section>
<section class="question">
<h4>Ask yourself...</h4>
<h2>Are there parts of the card that are "must have", "should have", "could have" or "would like"?</h2>
</section>
<section class="explanation">
<h2>Are there parts of the card that are "must have", "should have", "could have" or "would like"?</h2>
<h3>Why does it matters</h3>
<p>All requirements are important, however, to deliver the greatest and most immediate business benefits early the requirements must be prioritized.</p>
<ul>
<li><strong>Must have:</strong> critical to the current delivery timebox in order for it to be a success. MUST also be considered an backronym for the Minimum Usable Subset.</li>
<li><strong>Should have:</strong> important but not necessary for delivery in the current delivery timebox.</li>
<li><strong>Could have:</strong> desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.</li>
<li><strong>Would like:</strong> items that have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time.</li>
</ul>
<h3>What to do</h3>
<p>Keep the parts that that are Must and Should haves in this epic, and create smaller ones for could haves, and other ones for "Would likes".</p>
</section>
</section>
<section>
<section class="question">
<h4>Ask yourself...</h4>
<h2>Are there more than one user case?</h2>
</section>
<section class="explanation">
<h2>Are there different parts of this card that are "Must Have", "Should Have", "Could Have" or "Nice to Have"?</h2>
<h3>Why does it matters</h3>
<p>Use Cases are used to define and delimit the epic's scope once we try to get the user's point of view to set the requirements and achieve the impact. If we didn't, we could create epics with many scopes, and it will impact the complexity and deadline.</p>
<h3>What to do</h3>
<p>We suggest epics with one user case, that is, we need to answer just one issue using the user point of view.</p>
</section>
</section>
</div>
<!--
TEMPLATE
<section>
<section class="question">
<h4>Ask yourself...</h4>
<h2></h2>
</section>
<section class="explanation">
<h2></h2>
<h3>Why does it matters</h3>
<p></p>
<h3>What to do</h3>
<p></p>
<h3>Learn more</h3>
<p></p>
</section>
</section>
-->
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.min.js"></script>
<script>
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
dependencies: [
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true, condition: function() { return !!document.body.classList; } },
{ src: 'plugin/notes/notes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});
</script>
</body>
</html>