590769 Software Testing To Be Or Not To Be

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    590769 Software Testing To Be Or Not To Be - Presentation Transcript

    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 Hamlet
      Neha Thakur
    2. Objective
      To identify the various stakeholders, their involvement and to strategies the communication and the engagement needs of stakeholders
      To discuss various advantages, challenges and appropriate strategies
    3. Coverage
      Introduction
      Advantages of identifying and involving stakeholders
      Stakeholder analysis
      Stakeholder engagement and communication
      Challenges
      The 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 failures
      Software 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 propositions
      Out of six reasons cited for failures, five arerelated to communications between teams and stakeholders
      Poor planning and bad communication
      Scope — 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 product
      The effects of a service
      Stakeholder
    10. Advantages of identifying and involving
      Build 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 analysis
      SDLCmanagement
      Deliverymanagement
      Qualitymanagement
      • Requirements engineering
      • Application architecture and design
      • Data modeling
      • Coding and unit testing
      • Test definition
      • Test execution
      • Go live!
      • Transition
      • Project initiation
      • Project planning
      • Estimation
      • Project monitoring and control
      • Risk action assumption issues management
      • Supplier agreement management
      • Change control
      • Decision analysis and resolution
      • Project closure
      • Quality assurance
      • Metrics collection and reporting
      • Deliverable review
      • Defect prevention
      • Defect management
      Figure 1: Structured process area and process list of different management cycles
    12. Analyze your stakeholders
      Understand your stakeholders:
      What is their motivation?
      What are their expectations?
      What do we expect of them?
      Where are they?
      How expert are they at what they do?
      What is their availability?
    13. Analyze your stakeholders (cont.)
      Examples of categories you could use are:
      Decision makers (e.g., sponsors, artifact approvers)
      Information providers (e.g., Subject Matter Expertise)
      Regulatory (e.g., legal body, Center of excellence)
      Implementers (e.g., developers, testers)
      End users
      Post implementation support (e.g., trainers, managers)
    14. Stakeholder engagement and communication
      Stakeholder assessment
      • Identify the key stakeholders of the program and the extent to which they:
      • Need to be engaged
      • Require specific communication
      Stakeholder action plan
      • Outline a framework to manage stakeholder engagement and communications throughout the project
      Communication plan
      • Outline the detailed plan for communicating with key stakeholders throughout the project and establish responsibility for communication
      Figure 2: Stakeholder engagement Approach
    15. Engage stakeholders early and throughout the plan
      Plan should build trust over time and should allow for revisiting of the goals and project implementation
      Have a roadmap
      Be flexible
      Adhere to meeting times
      Facilitate the meetings skillfully
      Follow up
      Fundamentals
    16. Stakeholder engagement strategies
      Commitment Level: Advocacy & Ownership
      Engagement strategy: Position as Champion
      Low ABILITY TO INFLUENCE§ High
      Commitment Level: Commitment & Action
      Engagement Strategy: Involve extensively
      Commitment level: Understanding
      Engagement Strategy: Address concerns
      Low DESIRED COMMITMENT High
      High PROJECT IMPACT^ Low
      Commitment Level: Awareness
      Engagement Strategy: Keep informed
      Commitment Level: Support & buy-in
      Engagement Strategy: Enlist as needed
      Start-up TIME Vision Achieved
      Figure 3:Stakeholder engagement map
    17. Stakeholder engagement plan
      Figure 4: Stakeholder engagement assessment and action plan
    18. Stakeholder communication plan
      Figure 5: Stakeholder communication needs assessment and action plan
      Figure 6: Stakeholder communication plan
    19. Commitment versus time
      Engagement
      Individuals are actively involved in and contribute to Project activities.
      Acceptance
      Individuals are receptive to working with and implementing Project changes amid uncertainty.
      Understanding
      Individuals have an appreciation for the impacts and benefits that the Project will have on their functional areas.
      Awareness
      Individuals have heard that the Project exists and are aware of basic scope of the Project and general concepts.
      Commitment
      Ownership
      Individuals acknowledge that the Project belongs to them and create innovative ways to use and improve it.
      Status quo
      Time
      Vision
      Figure 7: Stakeholder commitment versus time graph
    20. Inadequate communication
      Constraints on time and money
      Pressures to meet schedules
      Inappropriate planning
      Little or no monitoring and evaluation process of interaction
      Challenges
    21. Stories/Case Study
      A leading global asset management firm announced merger of equal in late 2006 targeting close in mid 2007. The publicly announced target was more than half a billion dollars in cost reduction fully captured in five years. Deloitte was engaged to assist pre close planning, post close tracking, tools/system/framework development, enterprise wide base lining and non personnel expense execution. The mobilization of cross functional experts/staff and leverage of proprietary benchmarks and methodologies helped the firms successfully delivered/exceeded target slotted for the first six months of closing. In particular, the team achieved 40% cost saving in one major procurement category alone, which involved engaging close to 100 business stakeholders and gathering thousands of detailed specifications.
    22. Stories/Case Study
      As a small credit union in the Vancouver area, Vancity was founded on principles of community and has won numerous awards for its work around sustainability and climate change. With a re-branding effort that included an opportunity to better highlight its sustainability efforts, Vancity actively engages members and prospective members through new social media channels, member forums, unique brand campaigns, educational activities, and numerous opportunities for stakeholder feedback. As a result, brand preference went up by 30% and Vancity announced that it became carbon-neutral at the end of 2007, two years ahead of plan. As part of this effort, Vancity recorded more than $2 million in cost savings since 1992 through reductions in energy usage alone.
    23. References
    24. Questions?
    25. Thank you
    26. Contact:
      nethakur@deloitte.com
      thakurne@gmail.com
    27. About DeloitteDeloitte refers to one or more of Deloitte Touche Tohmatsu, a Swiss Verein, and its network of member firms, each of which is a legally separate and independent entity. Please see www.deloitte.com/about for a detailed description of the legal structure of Deloitte Touche Tohmatsu and its member firms. Please see www.deloitte.com/us/about for a detailed description of the legal structure of Deloitte LLP and its subsidiaries.Copyright © 2009 Deloitte Development LLC. All rights reserved.Member of Deloitte Touche Tohmatsu

    + thakurnethakurne, 2 months ago

    custom

    141 views, 0 favs, 0 embeds more stats

    Whitepaper Presented at CAST09, “Software Testing more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 141
      • 141 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 19
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories