Welcome to the ultimate article of the Introducing QA sequence. Should you learn the previous articles on this sequence, and I hope you probably did, you already know that QA has to do with bettering processes and testing. And you already know that high quality is a transferring goal. Our intention is to enhance the standard of your subsequent challenge.
Partly 1 of this sequence, we talked about how the Challenge Administration Workplace (PMO) is specializing in methods to supply extra worth to initiatives inside ITS. So in case you are contemplating a brand new challenge, chances are you’ll be pondering, “what can the PMO do for us?” The PMO as a complete has rather a lot to supply, and I can guarantee you that the entire is bigger than the sum of our components. However for the aim of this text, I’ll focus totally on the QA half. (Though, it’s typically troublesome to separate.)
Now we have been utilizing Software program as a Service (SaaS) increasingly more in our initiatives at UConn currently. Meaning the standard of the software program itself is considerably out of our arms. We’re relying on the provider of that software program to have superb QA practices. This additionally adjustments the best way testing is completed. As a substitute of precise testing for defects, we usually tend to examine that the mixing was accomplished accurately. We’ll insure that no matter software program we select matches effectively with the entire methods it wants to attach with at UConn: KFS, HR and Payroll methods, Scholar methods, numerous databases, and rather more. This all begins by accurately figuring out the enhancements we wish to make.
Listed here are just a few areas the place I consider QA can assist.
Necessities Overview: Necessities exist whether or not you write them down or not. I’ll work with the Enterprise Analyst (BA) and the challenge stakeholders to assessment the necessities. We have to make sure that all necessities are measurable. If they’re measurable, they’re testable. If we can not discover a measurement for a requirement, then it isn’t actually a requirement, however merely an idle thought.
Documentation Overview: The product’s documentation consists of the person/coaching manuals, set up information, on-line assist, or the rest that explains how you can use the system. We’re involved with bettering its accuracy, completeness, readability, ease of use, and the diploma to which it captures the spirit of the design for UConn.
Take a look at Planning: Right here we can assist to find out the perfect check technique. The who, what, why, when, the place, and the way of the testing course of. Do we want check instances, situations, one spherical, two rounds, extra? Do we now have the correct atmosphere? If we want person testing, do we have to practice the customers?
It’s value noting right here that the check plan doc is a dynamic doc that must be referred to typically. For that cause, it’s my intention to maintain it quick and easy: one or two pages max.
Take a look at Coaching: we are able to present periodic testing workshops to coach customers how you can acknowledge and report points once they happen. In these workshops, we may even make clear some testing phrases so after we discuss, we’re talking the identical language.
Classes Discovered: After all the PMO will do a “classes realized” exercise on the finish of each challenge, however I shall be taking a essential take a look at the QA features to see what labored and what didn’t. Now we have come away with “classes realized” from each challenge we now have achieved thus far. Moreover, the entire testing outcomes have been documented for future reference and audit functions as needed.
Steady Enchancment: There are two areas of enchancment we’re involved with; our QA expertise and the product that was simply put in or up to date. We’re at all times searching for methods to streamline the QA course of, based mostly on the context of the challenge. We additionally wish to make sure that the product (improve, integration, and so forth.) continues to work effectively effectively after the challenge is over. We can assist to arrange a course of for reporting issues going ahead.
Discover that nearly the entire areas talked about above are shared with no less than one different member of the PMO crew. We’re an built-in group and far of what we do blends backwards and forwards with different members. There could also be extra methods we can assist; we simply haven’t discovered them but, however we’re at all times trying.
A Worth Add
I see the QA operate as a price add to any challenge beneath the PMO. To that finish, listed below are the core values that I personally attempt to uphold on any challenge.
- I don’t declare to guarantee, guarantee, or management high quality. I don’t management something concerning the product. A tester is a witness, and in that capability, I attempt to help the standard creation course of.
- I attempt to keep up an inexpensive impartiality. The aim of testing is to solid mild on the standing of the challenge and its context.
- I’ll report every thing that I consider, in good religion, to be a menace to the challenge or to the customers thereof, in accordance with my understanding of the perfect pursuits of the stakeholders.
- I’ll repeatedly research my craft, be alert to higher options, and to higher methods of working.
Thanks for studying!
Mick
Associated articles:
Introducing QA Half 1: What’s QA?
Introducing QA Half 2: What’s High quality?
Introducing QA Half 3: What’s Testing?