1) The document discusses stakeholder identification, engagement, and communication strategies for software testing projects. It outlines the advantages of involving stakeholders and analyzing their needs, roles, and levels of commitment over time. 2) Common reasons for major software failures are discussed, including poor communication between teams and stakeholders that leads to ambiguous requirements and goals. 3) Effective stakeholder engagement requires early and ongoing communication through activities like status updates, meetings, and feedback opportunities to build trust and commitment to the project.

1. “Software Testing To Be or Not To Be” Conference of the Association for Software Testing July 15, 2009“To be or not to be, that is the question”– William Shakespeare’s HamletNeha Thakur

2. ObjectiveTo identify the various stakeholders, their involvement and to strategies the communication and the engagement needs of stakeholdersTo discuss various advantages, challenges and appropriate strategies

3. CoverageIntroductionAdvantages of identifying and involving stakeholdersStakeholder analysisStakeholder engagement and communicationChallengesThe appropriate strategy

4. Need for testing:Only testing can demonstrate that quality has been achieved.Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate.(Source: Wikipedia)In spite of performing testing, Why major software fails?Introduction

5. Fact sheet

6. Software failuresSoftware bugs are costing the U.S. economy an estimated $59.5 billion each year.(Source: WASHINGTON (COMPUTERWORLD))A May 2005 newspaper article reported that a major hybrid car manufacturer had to install a software fix on 20,000 vehicles due to problems with invalid engine warning lights and occasional stalling. On June 4 1996, the first flight of the European Space Agency's new Ariane 5 rocket failed shortly after launching, resulting in an estimated uninsured loss of $0.5 billion dollars.In early 1999, a major computer game company recalled all copies of a popular new product due to software problems.

7. So, what went wrong?Major software fails due to shortfalls in skills to deal with stakeholder value propositionsOut of six reasons cited for failures, five arerelated to communications between teams and stakeholdersPoor planning and bad communicationScope — stakeholders — goals, we rarely see testers involved to drive out any ambiguities or inconsistencies in these crucial deliverables

8. All about stakeholders

9. Who is a stakeholder?Are entities who areaffected by:The success or failure of a project The actions or inactions of a productThe effects of a serviceStakeholder

10. Advantages of identifying and involvingBuild organizational buy-in, mutual trust, commitment and capability.Reduced litigation/opposition to project implementation that results from the plan.The introduction of new perspectives and diverse interests into the planning process.Respect among adversarial advocacy groups and varied stakeholders across organizations of varied interest with varied POV (point of view)Incorporation of an open-minded and broad search for creative alternatives.Maximize the potential for a successful project from current to future state.Ensure the right people receive the right information, at the right time, in the right way.Ensure the right people participate at the right time, in the right way.In order to proactively increase stakeholder commitment to change over time stakeholder engagement is required.

11. Stakeholder analysisSDLCmanagementDeliverymanagementQualitymanagementRequirements engineering

12. Application architecture and design

13. Data modeling

14. Coding and unit testing

15. Test definition

16. Test execution

17. Go live!

18. Transition

19. Project initiation

20. Project planning

21. Estimation

22. Project monitoring and control

23. Risk action assumption issues management

24. Supplier agreement management

25. Change control

26. Decision analysis and resolution

27. Project closure