[Bibliography 20150309] The way the software wins: Strategies to execute

The 1th chapter is related to software in every business
1.1 Principles of software Management
1.2 Why is it that every business is software-related
1.3 We are engaged in hardware business
1.4 Maintaining the uniqueness of the product
1.5 Better quality than progress
1.6 In terms of software, what must happen often does not--
1.7 Quality Commitment
1.8 Summary and conclusion
Reference documents
2nd. Why the project failed
2.1 Emergency projects on the verge of failure
2.2 Reasons for Project failure
2.2.1 Unrealistic Schedule
Improper staffing of 2.2.2
2.2.3 changes in requirements during software development
2.2.4 Low-quality work
2.2.5 Believe in Miracles
2.3 Roles of supervisors in failed projects
2.4 Summary and conclusion
Reference documents
3rd Chapter Rational Management
3.1 Face Reality
3.2 Shorten the cycle
3.3 The business of breaking the door
3.4 Mastering The Facts
3.5 Final date of flight test
3.6 Nature of Rational management
3.7 Summary and conclusion
4th. Reasons for Quality Assurance
4.1 Low-quality software may endanger life safety
4.2 High-quality work saves time and money
4.3 Troubleshooting policies
4.4 High-quality work with higher predictable testability
4.5 Software quality must be managed
4.6 Summary and conclusion
Reference documents
The 5th chapter of the goal of leadership
5.1 Faster, better and more economical
5.2 Adjusting how your organization's software works
5.3 Setting goals
5.4 Accelerating work doesn't just mean shortening the timetable
5.5 Lifting Quality
5.6 Cost reduction
5.7 Improving task Time
5.8 Determination of responsibility
5.9 Summary and conclusion
Reference documents
The 6th chapter changes the engineering behavior
6.1 What to do instead of how to do
6.2 Discipline-based software practices
6.3 Convincing the others
6.4 PSP Course
6.5 Back to the original point
6.6 Summary and conclusion
Reference documents
The 7th chapter builds up the positive team
7.1 EBS's Brokernet Team
Development of 7.2 tsp
7.3 How to build a positive team
7.4 Teradyne Team
7.5 Final Results
7.6 How to motivate your team
7.7 Build a responsible team
7.8 EBS Results
7.9 Environment of trust
7.10 Consequences of a project completion date that cannot be achieved
7.11 Keeping the team stable
7.12 Summary and conclusion
Reference documents
8th. Benefits of Team work
8.1 Better Predictability
8.2 Shorter production cycles
8.3 Reduce development costs
8.4 Improve product quality
8.5 Reducing the rate of change in personnel
8.6 tsp introduction cost
8.7 Return on Investment
8.8 Discounted return on investment
8.9 Summary and conclusion
Reference documents
Chapter 9th Next Steps
9.1 7 Transition Steps
9.2 Action Plan
9.3 Summary and conclusion
Appendix A TSP process
A.1 TSP overview
A.2 Team Preparation
A.3 TSP training
A.4 not enough team to prepare
A.5 Summary
Appendix B forming a TSP team
B.1 Build TSP team
B.2 First Management Meeting
B.3 Team Questions
B.4 First meeting Example
b.4.1 Supervisor Absent
b.4.2 lack of emphasis on demand
B.4.3 's busy CEO
B.5 discussing issues during the formation
B.6 Last Management meeting
B.7 Summary
Reference documents
Appendix C Project Plan Review
The role of C.1 supervisor in team building
C.2 Last Management meeting
C.3 Formation Products
C.4 Program Briefing
C.5 Plan Evaluation Checklist
C.6 Business Assessment
c.6.1 team plans to meet or exceed targets
c.6.2 team needs to increase resources
The c.6.3 team is unable to meet the goal
C.7 Plan Evaluation
c.7.1 Conceptual Design
c.7.2 scale Estimation
c.7.3 Production Rate Estimation
c.7.4 tasks when measured
C.8 Plan Comparison Example
C.9 Quality Plan Evaluation
c.10 Plan Evaluation
Risk assessment of C.11 inspection team
C.12 meeting Ends
c.13 Summary
Appendix D Quarterly Review of projects
D.1 the reason for the review by the supervisor
Items to be considered in D.2 Project review
d.2.1 Progress Management
d.2.2 Team Initiative
D.3 Review Strategy
D.4 Review Process
D.5 time to perform the first review
D.6 Initial Stage Review
d.6.1 issues related to planning
d.6.2 Questions about Tasks
d.6.3 questions about the value that has been obtained
d.6.4 Completion Forecast
d.6.5 issues related to workload balance
d.6.6 questions about the time record
d.6.7 issues related to program size records
D.7 Standard Stage Review
D.8 Summary
Appendix E Standard Stage Review
E.1 Correction Rate Management
E.2 issues to be considered during the review
E.3 Fault Logging
E.4 Standard Stage Review
e.4.1 Fault Map
e.4.2 issues related to review rates
e.4.3 the problem of failure rate in each stage
e.4.4 about correction Rate management issues
e.4.5 problems with fault density
e.4.6 issues related to benchmark comparisons
E.5 Summary
Reference documents
Appendix F Return on Investment
F.1 Improvement Results Summary
F.2 Introduction Strategy
e.2.1 Minimum Time Introduction strategy
e.2.2 Minimum cost Introduction strategy
F.3 Return on Investment
e.3.1 tsp introduction cost
e.3.2 cost savings after introduction of TSP
F.4 Discounted return on investment
F.5 Summary
Reference documents

[Bibliography 20150309] The way the software wins: Strategies to execute