Resource
Article [7180]
General
[1032]
Acceptance
[63]
Ad Hoc
[28]
Agile, Scrum
[231]
Black Box
[117]
Bug, Defect
[258]
DB, Test Data
[274]
Environment
[42]
Functional
[115]
Glossary, Term
[74]
GUI, Usability
[98]
Integrate test
[46]
Interview, FAQ
[285]
Manual Testing
[117]
Methodology
[231]
Metrics
[327]
Mobile, Embed
[153]
Performance
[326]
Process
[194]
Requirement
[124]
Review, Static
[102]
Risk
[99]
Security Test
[215]
Standard, ISO
[179]
Test Automate
[347]
Test Case
[341]
Test Design
[69]
Test Plan
[311]
Test Manage
[227]
Test Script
[56]
Test Technique
[265]
Tool
[175]
Tool- Jmeter
[40]
Tool- Selenium
[125]
Unit Test
[166]
Web Test
[258]
White Box
[70]
Ebook [1163]
General
[277]
Acceptance
[3]
Agile, Scrum
[24]
DB Test
[76]
Development
[137]
GUI, Usability
[17]
Interview, FAQ
[9]
Java Test
[68]
Metrics
[17]
Mobile, Embed
[14]
Performance
[49]
Process
[11]
Requirement
[55]
Review, Analysis
[8]
Risk
[7]
Security Test
[71]
Standard
[20]
Test Manage
[85]
Test Automate
[84]
Tool
[8]
Unit Test
[67]
Web Test
[60]
Testing Tool [2277]
Acceptance
[25]
Agile, Scrum
[43]
Bug Tracking
[127]
Build, Release
[27]
Environment
[58]
DB, Test Data
[83]
Functional
[240]
GUI, Usability
[79]
Java Test
[71]
Metrics
[57]
Mobile, Embed
[79]
Network Test
[67]
Performance
[222]
Requirement
[62]
Review, Static
[105]
Security Test
[111]
Test Design
[52]
Test Manage
[208]
Unit, Debug
[224]
Utility, Capture
[97]
Web Testing
[234]
Video [622]
News [2773]
Webinar [914]
Certification Resource
CTAL [273]
CTEL [36]
CSTE, CSQA [198]
CSQE [41]
CMMI, TMMI [135]
PMP [114]
ITIL [67]
Six Sigma [41]
Other [81]
Forum
Forum [1935]
Book
[56]
Certification
[48]
Conference
[64]
ISTQB
[158]
QTP
[92]
Software Test
[1062]
Standard, ISO
[89]
Testing Tool
[287]
What makes us think of risks? Is it backward thinking or forward thinking?
Will it allow us to grow and progress or slow us down? Such questions confront us when we think of risk management. In growth-oriented management cultures of the past, negative aspects were not mentioned. The drive was to reach out and move ahead. In those days, to reflect upon failure was a sign of weakness. The entrepreneur was a go-getter who crossed all barriers and achieved. Thinking about failure came into management paradigms through different avenues. First, the market demanded fail-safe products. The product developer was forced to look at failure possibilities and come up with a robust design. He struggled to remove what we refer to today as “product risks.” The discipline of technology management accepted risk thinking rather elegantly. It made sense to product developers to design a product with minimum risks for the user. The success of risk management in product development also fuelled technological progress and expansion. To identify product risks, a fuller and more mature technical knowledge was required. It was not a smooth beginning. Although designers enjoyed the creative
pleasures and excitement of design, they disliked risk analysis of their products. In due course, product risk analysis was accepted by the industry. Second, for finance management, risk became an investment question. Credit risk was studied, defined, and measured religiously in finance institutions. Variation in ROI was a measure of risk, striking a sympathetic chord with the age-old concept that “variation is trouble.
Service
New
Popular Documents
Weekly
Monthly
Yearly
Popular Download
Weekly
Monthly
Twitter
Tag List
outsourcing software testing
tool
Selenium
web testing
Questions
software qa service
HP
Test management
Metrics
Test
Performance Testing
Software
agile
Test Automation
Interview
Sql
software testing company
Automation
conference
QTP
Quality
security testing
PM
security
Development
Test Case
Software Testing
QA
Bug
testing
mobile
Plan
Sample Exam
tester
performance
Manual
agile testing
Unit Testing
mobile application testing
process
framework
Guide
Certification
Exam
checklist
web
mobile testing
ISTQB
Template
test plan
Management
Visitor
Member Login (IP)
225010
59488
203105206
Yesterday
Today
Total

 
 
B.Minh
Thanks