TestSheepNZ.github.io/test-plan-dashboard.html at master · hiangeel/TestSheepNZ.github.io · GitHub

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
170
171
172
173
174
175
176
177
178
179
<!DOCTYPE html>
<html lang="en">

<head>

  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
  <meta name="description" content="Test Plan Dashboard">
  <meta name="author" content="TestSheepNZ">

  <title>The Number Game - Instructions</title>

  <!-- Bootstrap core CSS -->
  <link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">

  <!-- Custom fonts for this template -->
  <link href="vendor/fontawesome-free/css/all.min.css" rel="stylesheet" type="text/css">
  <link href="https://fonts.googleapis.com/css?family=Montserrat:400,700" rel="stylesheet" type="text/css">
  <link href='https://fonts.googleapis.com/css?family=Kaushan+Script' rel='stylesheet' type='text/css'>
  <link href='https://fonts.googleapis.com/css?family=Droid+Serif:400,700,400italic,700italic' rel='stylesheet' type='text/css'>
  <link href='https://fonts.googleapis.com/css?family=Roboto+Slab:400,100,300,700' rel='stylesheet' type='text/css'>

  <!-- Custom styles for this template -->
  <link href="css/agency.min.css" rel="stylesheet">

  <link rel="stylesheet" href="css/bootstrap.min.css">
  <link rel="shortcut icon" href="img/testsheep.ico" type="image/x-icon" />
  <link rel="icon" href="img/testsheep.ico">

</head>

<body id="page-top">

  <!-- Navigation -->
  <nav class="navbar navbar-expand-lg navbar-dark fixed-top" id="mainNav">
    <div id="mainNavigation"></div>
  </nav>


  <!-- Header -->
  <header class="masthead">
    <div class="container">
      <div class="intro-text">
          <div class="intro-heading text-uppercase">Test Plan Dashboard</div>
          <div class="intro-lead-in">Make your testing visible</div>
      </div>
    </div>
  </header>

  <!-- Contents -->
  <section class="bg-light page-section" id="testplandash">
    <div class="container" >
        <div class="row" >
            <div class="col-lg-12 text-left">

                <p>This article was originally published in my blog <a href="http://testsheepnz.blogspot.com/2013/05/the-test-plan-dashboard.html">here</a>.</p>
                <p></p>

                <p>This week I needed help develop a test plan for use in another area in the business, and found myself digging out my tried-and trusted <b>Test Plan Dashboard (TPD)</b> template.</p>
                <p>The TPD is something I developed back at Kiwibank (through the suggestion of my line manager, Matt Winter), to have a simple, A3 sheet way of displaying what was planned for testing, in order to share with stakeholders and project managers.</p>

                <p>Using "an example right now would be useful", here is is filled out for a totally fictional project, the “Paint Mixer 2000” (by the way, if you're wondering, Mitre 10 is a New Zealand hardware chain),</p>

                <img height=auto width="100%" src="img/testdashboard.jpg">

                <p>I’ve found it to be an invaluable resource to help me fill out the big questions around the testing project.  Questions which of course all testers will be familiar with,</p>

								<ul>
									<li>Introduction – what is the project all about?</li>
									<li>In-Scope – what will we be testing?</li>
									<li>Out-Of-Scope – what won’t we be testing?</li>
                  <li>Entry Conditions – when can we start?</li>
                  <li>Exit Conditions – when can say we’re done?</li>
                  <li>Timescales – how long do we think it’ll take?</li>
                  <li>People – who’ll be working on the project?</li>
                  <li>Test Environment – where will we best testing on?</li>
                  <li>Risks – what could go wrong?</li>
								</ul>

                <p><i>Put it to the test now.  Enlarge the image of the Paint Mixer 2000 TPD picture, and see if in just a few minutes you feel comfortable about what the product is, and what will be tested.</i></p>

                <p>I’ve had phenomenal feedback from the TPD.  Originally designed as a tool to summarise a test plan, I’ve actually used it to revise the way I approach test planning over the years.  Instead of being derived from the test plan, I now use it as a consulting tool to help me build a test plan/strategy on medium to large projects, or as a substitute for a large plan on much smaller projects.</p>

                <p>When I was on huge integration projects with a lot of testing elements (many of which you can't hope to be an expert in), I would take a blank copy around all the testing sections (including those external areas) and talk with the experienced testers there in that field or on that technology, and together we’d fill in and scope out what their testing phase would look like.     </p>

                <p>If you sit together with the experts, you can fill it in on your laptop within about 15-30 minutes, but rather than asking for a test plan at a later date and reviewing, the session is interactive and you can make enquiries of them, adding elements to either the In-Scope or Out-Of-Scope as you go.</p>

                <p>Go around each section, and put a whole group of these together, which can be posted on the wall.  It’s like putting together pieces of a testing jigsaw.  Now when you’re looking at creating your master test plan, you can try to draw up who will be focusing on what – you may find there are some elements which simply don’t have a home, and maybe you need to negotiate to get them tested in a certain phase by yourself or an outside party.  It’s a great tool for building a big picture.</p>

                <p>And as I learned from the BAs who I worked alongside with at Kiwibank, and used similar tools - it's about harnessing together a collaborated plan, which everyone feels listened to and ownership of, and harnesses everyone's expertise</p>

                <p>Last year when I was working on the <a href="http://testingcircus.com/editions/testing-circus-2012-november-edition">Building A Test Culture</a> article that was published in the Testing Circus magazine, I was struck by something Janet Gregory said about “make testing visible”.  It’s a comment that gripped me from the moment I read it, and still does.</p>

                <p>There is a lot of mystery around testing – much of this leads to misunderstanding.  That makes many testers understandably annoyed.  However for us as testers, the ball is squarely in our court to try and remove that.  I think the TPD is one way to do just that, because it’s a very visual way to look at what our testing charter and constraints are, and unlike a plan that’s kept in a draw, this can be kept on a wall, on display for all to see.  But not just for project managers and business owners – it should be visible for all testers as well, so they are comfortable about what they are testing to, and what the project goals are.</p>

                <p><i>So have a go at making your own, play with it, get feedback and see if it helps to make testing more visible for you.</i> You can download my word template <a href="docs/PlanDashboard - sample.docx">here</a>.</p>

								<p>

            </div>
        </div>
    </div>
  </section>


  <!-- Modal 1 -->
  <div class="portfolio-modal modal fade" id="termsModal" tabindex="-1" role="dialog" aria-hidden="true"></div>

  <!-- Modal 2 -->
  <div class="portfolio-modal modal fade" id="aboutModal" tabindex="-1" role="dialog" aria-hidden="true"></div>

  <!-- Footer -->
  <footer class="footer">
    <div class="container">
      <div class="row">
        <div class="col-md-4">
          <span class="copyright">Copyright &copy; Mike Talks 2019</span>
        </div>
        <div class="col-md-4">
          <ul class="list-inline social-buttons">
            <li class="list-inline-item">
              <a href="https://twitter.com/TestSheepNZ">
                <i class="fab fa-twitter"></i>
              </a>
            </li>
            <li class="list-inline-item" hidden>
              <a href="#">
                <i class="fab fa-facebook-f"></i>
              </a>
            </li>
            <li class="list-inline-item">
              <a href="https://www.linkedin.com/in/mike-talks-3423348/">
                <i class="fab fa-linkedin-in"></i>
              </a>
            </li>
          </ul>
        </div>
        <div class="col-md-4">
          <ul class="list-inline quicklinks">
            <li class="list-inline-item" >
              <a data-toggle="modal" href="#aboutModal">About</a>
            </li>
            <li class="list-inline-item">
              <a data-toggle="modal" href="#termsModal">Terms of Use</a>
            </li>
          </ul>
        </div>
      </div>
    </div>
  </footer>

  <!-- Bootstrap core JavaScript -->
  <script src="vendor/jquery/jquery.min.js"></script>
  <script src="vendor/bootstrap/js/bootstrap.bundle.min.js"></script>

  <!-- Plugin JavaScript -->
  <script src="vendor/jquery-easing/jquery.easing.min.js"></script>

  <!-- Contact form JavaScript -->
  <script src="js/jqBootstrapValidation.js"></script>
  <script src="js/contact_me.js"></script>

  <!-- Custom scripts for this template -->
  <script src="js/agency.min.js"></script>

  <!-- Sets up the header-->
  <script src="js/main.navigation.js"></script>

  <!-- Footer Modals -->
  <script src="js/footer.modals.js"></script>

</body>


</html>