February 2009
Intermediate to advanced
208 pages
2h 55m
English
book
The Next Leap in Productivity: What Top Managers Really Need to Know about Information Technology
by Adam Kolawa
Content preview from The Next Leap in Productivity: What Top Managers Really Need to Know about Information Technology
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
4.9. The Right Way and the Wrong Way to Measure Quality
You cannot get to good software unless you think about quality the right way, and you cannot think the right way if you do not have the right language to form your concepts. Too many IT managers think of a "defect" as being the same thing as a "software bug," that is, something broken in the program. They view the role of the Quality Assurance group to be to find and report bugs for the development team to fix.
This is wrong for two reasons. It is the wrong understanding of what a defect is, and it is the wrong role for QA.
As opposed to most IT managers, when I say defect, I do not mean only "bug," I mean anything produced by the development team that is less than good.
A defect might be in the code, or it might be in the requirements document, or in the design models or in the tests. A defect might be a bug—or it might be an oversight, an inconsistency, or a sloppily defined requirement.
Defects can originate in any of the phases of the development cycle, from requirements through design and construction, all the way to maintenance and support. If your QA team is looking for bugs and only bugs, you have a problem.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.