Difference between revisions of "Main Page"
m |
m (→Getting started) |
||
| Line 7: | Line 7: | ||
<imagemap> | <imagemap> | ||
| − | Image:PDCA_SQARd_w_logo.PNG|thumb|right|250px|alt= | + | Image:PDCA_SQARd_w_logo.PNG|thumb|right|250px|alt=SQA² PDCA Cycle|SQA² PDCA Cycle |
| − | rect 85 82 203 201 [[Team_Home_Page_Team| | + | rect 85 82 203 201 [[Team_Home_Page_Team|SQA² Team Home Page]] |
poly 3 1 124 2 163 41 134 80 86 81 84 141 41 115 2 150 [[PDCA#PLAN|Plan]] | poly 3 1 124 2 163 41 134 80 86 81 84 141 41 115 2 150 [[PDCA#PLAN|Plan]] | ||
poly 137 1 280 3 281 123 243 160 205 132 205 81 147 79 [[PDCA#DO|Do]] | poly 137 1 280 3 281 123 243 160 205 132 205 81 147 79 [[PDCA#DO|Do]] | ||
| Line 23: | Line 23: | ||
:* '''TOOLS''' - Used to support (not replace) the process | :* '''TOOLS''' - Used to support (not replace) the process | ||
| − | SQA² subscribes to the Context-Driven school of testing. There is no "one size fits all" approach to software QA methodology. Underpinning all our processes is the [[PDCA]] process developed by W. Edwards Deming in the 1950s. The continuous improvement process is best described by the diagram showing the [[PDCA]] feedback loop used at | + | SQA² subscribes to the Context-Driven school of testing. There is no "one size fits all" approach to software QA methodology. Underpinning all our processes is the [[PDCA]] process developed by W. Edwards Deming in the 1950s. The continuous improvement process is best described by the diagram showing the [[PDCA]] feedback loop used at SQA² (shown right). The continuous process is described below: |
:* '''PLAN''' - Design or revise business process components to improve results | :* '''PLAN''' - Design or revise business process components to improve results | ||
Revision as of 19:17, 7 November 2014
Team Site for SQA²
Getting started
The first step on the road to exceeding your customer's expectations is to establish a process that will support your customers' unique goals and needs of their organization.
The Team at SQA² helps our business partners define and implement a more effective software quality-assurance process. We can demonstrate that a better software QA process leads not only to more satisfied customers, but also to shorten the time-to-market timelines while at the same time reducing costs for support and maintenance.
An effective software quality methodology incorporates:
- PROCESS - Documented procedures to guide and support users of the methodology
- PEOPLE - Management leadership; training and support for all participants
- TOOLS - Used to support (not replace) the process
SQA² subscribes to the Context-Driven school of testing. There is no "one size fits all" approach to software QA methodology. Underpinning all our processes is the PDCA process developed by W. Edwards Deming in the 1950s. The continuous improvement process is best described by the diagram showing the PDCA feedback loop used at SQA² (shown right). The continuous process is described below:
- PLAN - Design or revise business process components to improve results
- DO - Implement the plan and measure its performance
- CHECK - Assess the measurements and report the results to decision makers
- ADJUST - Decide on changes needed to improve the process
See Also:
- New Employee Onboarding / Employee Critical Path Must Know
- SQA² Team / SQaaS Wiki Index
- Weekly Learning List For Employees
- All Wiki Pages Index
- All Wiki Categories
- Learning Resources For All Employees
- Standard Operating Procedures Overview
- SQA² Home Page
- SQA Resources Home Page(Old)
- Glossary of Terms/Definitions
