'Team Work Within The Test Team - (E2)Q + p + P = TW' by Malini Mohankumar
Upcoming SlideShare
Loading in...5
×
 

'Team Work Within The Test Team - (E2)Q + p + P = TW' by Malini Mohankumar

on

  • 380 views

 

Statistics

Views

Total Views
380
Views on SlideShare
380
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Title slide option [A] inclusive of image panel.

'Team Work Within The Test Team - (E2)Q + p + P = TW' by Malini Mohankumar 'Team Work Within The Test Team - (E2)Q + p + P = TW' by Malini Mohankumar Presentation Transcript

  • TEAM WORK WITHIN TEST TEAMMalini Mohan KumarHitachi Consulting, India
  • The “Top Ten” Skills shortages amonggraduates% ofemployerssurveyed1 Commercial Awareness 67%2 Communication Skills 64%3 Leadership 33%4 Ability to work in a team 33%5 Problem solving 32%6 Conceptual ability 21%7 Subject Knowledge & competence 19%8 Foreign languages 19%9 Numeracy 19%10 Good general education 15%Source: Association of Graduate Recruiters “Skills forGraduates in the 21st Century” www.agr.org.ukCopyright 2011 EuroSTAR Conferences. All rights reserved2
  • Why do some software testteams succeedwhile others fail?Copyright 2011 EuroSTAR Conferences. All rights reserved 3
  • Is itThe nature of specific tasks the team is assignedThe difference between success and failurethat the preordained, or otherwise out of theteams control?the key to success simply a matter of assembling acollection of "superstars" and then getting out oftheir way?Conversely, maybe success depends completely oneffective team leadership. Whats the answer here?Copyright 2011 EuroSTAR Conferences. All rights reserved 4
  • The short answer is that there is nosimple solution. Any team has to balanceits autonomy with the need to respondto external governing forces and inter-team responsibilities. Hiring stellarperformers can obviously help inbuilding a team, but its not a guaranteeof success.Copyright 2011 EuroSTAR Conferences. All rights reserved 5
  • IT companies need to bring testing upfront indelivery life-cycle to provide rapid feedback, buildautomated tests to allow rapid changes and involveall the stakeholders early to build the right valuetests.Copyright 2011 EuroSTAR Conferences. All rights reserved 6
  • To do these they need to invest in multi-skilledtesting professionals trained in cutting edge testmethodologies.Testers alone can’t bring efficiency in testing. Forthat there needs to be an increase in collaborationbetween testers and Business experts, testers anddevelopers and testers and end users.Copyright 2011 EuroSTAR Conferences. All rights reserved 7
  • Today World Key Word isCollaboration and thats a Key fordelivering values – Short ClippingsCopyright 2011 EuroSTAR Conferences. All rights reserved 8
  • Organizations which encourage use of agilemethods, new tools and techniques, cloudvirtualization which allow collaboration to happenare more likely to deal with changes efficiently.UAT TestingTest EnvironmentTest Execution and ReportingTest PlanningCollaboration Testing Principles and approach for developers and TestersCopyright 2011 EuroSTAR Conferences. All rights reserved 9
  • This is Joe. She works on project. She is a QACopyright 2011 EuroSTAR Conferences. All rights reserved 10
  • Joe sits in the corner….….. TestingCopyright 2011 EuroSTAR Conferences. All rights reserved 11
  • While others doesn’t bother what Joe is doing….Huddle……This is not sounding like team workCopyright 2011 EuroSTAR Conferences. All rights reserved 12
  • I Found a bug!Joe found a bug and tries to tell developersCopyright 2011 EuroSTAR Conferences. All rights reserved 13
  • But the project manager tells joe to not todiscuss with her team or developersand not to waste their timeThis is not sounding like team workCopyright 2011 EuroSTAR Conferences. All rights reserved 14
  • Joe’s team members finishes their test casepreparation and show it to Developers andBA but not to JoeJoe feels bad..This is not sounding like team workCopyright 2011 EuroSTAR Conferences. All rights reserved 15
  • Joes writes automation test scripts, she wants topair with her team and developersInstead the other team members,BA and developers….This is not sounding like team workCopyright 2011 EuroSTAR Conferences. All rights reserved 16
  • They don’t think its very important…Poor Joe use to feel bad..This is not sounding like team workCopyright 2011 EuroSTAR Conferences. All rights reserved 17
  • A week ago I foundthat the applicationdoesn’t match theclient acceptancecriteria but no onelisten to meBroken theacceptancecriteria! Found abug..My target offinding 20bugs for thisweek got overI couldn’t meetthe target..ohmy status..amworriedThis is not sounding like team workCopyright 2011 EuroSTAR Conferences. All rights reserved 18
  • I am the one whofind the bug soam the one goingto inform thedeveloper firstNo its me who foundit first so am the oneis going to informthe developerI already informto our TL aboutthis bugJoe thinks that its TL responsibilityto bring the team together todiscuss about the bug findingsThis is not sounding like team workTL Doesn’t seems to be botheredabout the team activitiesCopyright 2011 EuroSTAR Conferences. All rights reserved 19
  • Well done team!I have delivered theproduct and I amgoing on vacationCopyright 2011 EuroSTAR Conferences. All rights reserved 20
  • I asked for a race horseyou delivered me a cowDuhhhhh! Butstill its ananimal withfour legsCopyright 2011 EuroSTAR Conferences. All rights reserved 21
  • Quality of the software suffers from lack ofso many things like, Trust, responsibility,accountability, communicationIf only things could be better….Copyright 2011 EuroSTAR Conferences. All rights reserved 22
  • I am very happywith what youhave delivered tomeTeam lets celebrate oursuccess! Party timeguys..lets party!How this could have happen to them?Copyright 2011 EuroSTAR Conferences. All rights reserved 23
  • Blue print of Best Test TeamPair testingProject Manager appreciates the testerTest team work closely with each otherTeam members are synchCommunicates freelyCopyright 2011 EuroSTAR Conferences. All rights reserved 24
  • (E2)Q + p + P = TWE = EfficiencyE= EffectivenessQ= Qualityp=ProcessP=ProductivityTW= Team WorkThis is my equation to build Team Work – What is yours?Copyright 2011 EuroSTAR Conferences. All rights reserved 25
  • Why TeamTechnology is complex Interdisciplinary knowledge requiredAdvantage in diversityOne vision many handsShared responsibilityTiming is essentialCopyright 2011 EuroSTAR Conferences. All rights reserved 26
  • Collaborative Team WorkHave Trust and confidence in team membersLet go the EgoNot compete with each otherBe committed to the common goalCommunicate openly and directlyResolve conflict mutually and openlyEmpathize and understandRespect and support individual differencesResponsibility and accountability(E2)Q + p + P = TWEffective & Efficiency * QualityDevelop better World for Developers and TestersWhat Makes an effective team?What Makes an ineffective team?Copyright 2011 EuroSTAR Conferences. All rights reserved 27
  • Define, Designate and Development(E2)Q + p + P = TWProcess = Define, Designate & Develop teamDefine - WHO, WHAT & HOWDesignate : Who will do what - ResponsibilitiesDevelopment : Forming, Storming, Norming, Performing, AdjourningTucks Man ModelGetting the best out of key project resourcesCopyright 2011 EuroSTAR Conferences. All rights reserved 28
  • TuckMan’s Team ModelForming : “Nice to Meet you, not sure why we’re here, it looks like a lot of work!”Storming: “Do I HAVE to work with this team???”Norming: “Maybe we will be able to pull this all together, if we stop fighting and listen toeach other….”Performing: “We’ve got a great plan, and everyone is pulling together….”Adjourning: Goal accomplished, Project OverTeam Building ModelCopyright 2011 EuroSTAR Conferences. All rights reserved 29
  • Team Work ResultsTrust (Emotional intelligence)Accountability Communication(E2)Q + p + P = TWProductivity = Trust + Accountability + Communication+ People (Relationship)RelationshipCopyright 2011 EuroSTAR Conferences. All rights reserved 30
  • Advantage of (E2)Q + p + P = TWHighly focused on delivering necessary results.Clear up confusion on rapidly changing challenges and complex issues.Minimize conflicts in the team.Helps to think alternative ways to find more anomaliesHelp tester to focus on what is important rather what is irrelevant.Improve the overall team productivity and meet the budgetMake better decisions and Overall accountability increases.Prepared to adopt changeCommunicate clear and concise.See all sides of a situation to avoid being blindsided.More visibilityUtilization of workforceIncreased productivity and better quality of deliverablesCopyright 2011 EuroSTAR Conferences. All rights reserved 31
  • Recipe for Successful Team Beneficial Team Behaviors Clarity in Team Goals An Overall Project Framework Clearly Defined Roles Clear Communication Well-Defined Decision Procedures Established Ground Rules Awareness of the Group ProcessCopyright 2011 EuroSTAR Conferences. All rights reserved 32
  • Collaboration / Team Work(E2)Q + p + P = TWDefine clear Goal and logicalobjective for each team memberDevelop thought leadership andencourage innovative ideasto make things happenDevelop soft skillsCreativity, flexibility,communication,lateral and critical thinkingDiversityLesson Learntfrom set backsConstructive feedback at right timeFinal WordBuild relationshipCopyright 2011 EuroSTAR Conferences. All rights reserved 33
  • Final Word Energy Expertise (IQ) Emotional Intelligence (EQ)Daniel Goleman – Emotional IntelligenceSuccessful Organization in EQ not in IQCopyright 2011 EuroSTAR Conferences. All rights reserved 34
  • Summary Collaboration is the key Seek diversity in team constituency, both technical and otherwise Foster involvement and participation of all team members Understand to a degree, variations in contribution by team members Transfer team resources to solve the problems that appear most difficultCopyright 2011 EuroSTAR Conferences. All rights reserved 35
  • 36