ACT AS A TEAM WITH CUSTOMER HOW TO BUILD THE CUSTOMER TRUST & LESSONS LEARNED.

Slides:



Advertisements
Similar presentations
10 Rules To Manage Your Boss faster decisions, better decisions and more trust.
Advertisements

Welcome Back to School!!! Mr. Sortina.
Time Management By Zahira Gonzalez.
Gallup Q12 Definitions Notes to Managers
Session 2.3: Skills for Supportive Supervision
Click the mouse button to operate1 Apologising  Learning to say sorry is one of the most mature qualities you can acquire.  Apologising is one of those.
Evaluating Requirements. Outline Brief Review Stakeholder Review Requirements Analysis Summary Activity 1.
Applied Software Project Management Andrew Stellman & Jennifer Greenehttp:// Applied Software Project Management Introduction.
Applied Software Project Management INTRODUCTION Applied Software Project Management 1 5/20/2015.
Building a Strategic Action Team Texas Department of State Health Services McAllen, Texas 7/18/07.
Kodu Trials Celebration 11 December 2009 Evaluation of the Trials Ian Phillips, I & J Management Services.
Applied Software Project Management 1 Introduction Dr. Mengxia Zhu Computer Science Department Southern Illinois University Carbondale.
It begins with me… Feeling good about yourself and knowing that you deserve healthy relationships is VERY important! See the good in yourself and focus.
Building Human Resource Management Skills National Food Service Management Institute 1 Effective Leadership and Management Styles Objectives At the completion.
Effective Questioning in the classroom
Connections to Independence
thinking hats Six of Prepared by Eman A. Al Abdullah ©
Pair Programming Testing 2, October 14, Administration  Project due Monday 2PM SHARP  Remember all parts of documentation (list of tests, project.
15 Powerful Habits Make You The Winner!!!.
COLLABORATION MODULE #3 Planning Good Meetings An online module developed by Pivot Learning Partners for the West Contra Costa Unified School District.
Module 3 – Release Letting Go so your Team can Support you Effectively.
Take control of your personal effectiveness Cyprus 2015 Lucy Whitehall.
Managing the Unexpected …and keeping people safe at the same time Jason Rowley Group Health and Safety Director Carillion.
4 Basic Qualities of a Healthy Relationship
Introduction Managing time in organizations is difficult because time flows at the same rate for everyone and cannot be 'managed' like other resources.
Team Leadership AGED Thought for the day… “Strength lies in differences, not in similarities.” ~ Steven Covey.
Definitions Self-concept: Picture or perception of ourselves Self Esteem: Feelings we have about ourselves Self-ideal: The way we would like to be.
Chapter 6 – Resolving Conflicts What do you think of when you see these pictures? Why?
Colin Pritchard Driving School Customer Satisfaction Survey Results Last Updated 1 st January 2014.
Requirements Engineering Requirements Elicitation Process Lecture-9.
In all the talk of improving teaching and learning, sometimes – no, often – there is too much talk about the model OfSTED lesson. Too often this leads.
University of Sunderland ENGM92 Unit 4 ENGM92 Communication Unit 4.
SELF ESTEEM. WHAT IS SELF ESTEEM? Is the way we think and feel about ourselves. It can impact on our lives.
Establishing an Agile Testing Team: Our Four Favorite “Mistakes” Kay Johansen Anthony Perkins.
Student Norms The following norms were decided by YOU! If your goal is to have a successful year, here’s how to make your goal a REALITY!
HIF1O/2O Dating. Explain the difference between love and infatuation Identify ways to handle rejection Learning Goals.
© 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice 1 Knowing what to Position HP BAC.
Peer Pressure / Refusal Skills. Health Class Reminders Take out your Peer Pressure and Refusal Skills notes from last Friday. Take the first 10 minutes.
Introduction. Steve Semler The Session in a Nutshell Figure out the business purpose and learning intent. Determine what actions or decisions the learners.
Evaluating Requirements
Submitted to- prof.Dheeraj tiwari Submitted by – priyanka snehi.
Tips to Empower Your Team Employers often times want to empower their employees, but they don’t always know quite how to go about it. Empowering employees.
Dealing with Problems in Daily Life – Unit 337
Time Blocking Revisited. “It's not the will to win that matters... everyone has that. It's the will to prepare to win that matters.”
IT’S YOUR SHIP Captain D. Michael Abrashoff
Yeah but.. What do I do? Software Leadership Dan Fleck 2007.
Reviews Chapter 5 Applied Software Project Management, Stellman & Greene See also:
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
It’s not that uncommon to feel like you can’t relate to your parents.
Presented by The Solutions Group Decision Making Tools.
The Secret to Success (Really!) Performance Management Beth Burbage Vice President, Organizational Development Silverado Senior Living.
PROJECT MANAGEMENT Software Engineering CSE
Call on students to identify a difference of opinion they have had with someone. List several of them on the writing surface. Ask students to mention.
Conflict Management Technique
LIFE SKILLS What is the definition of a life skill?
Introverts CAN BE LEADERS TOO
HOME MEDICAL CARE Deming's 14-Point Philosophy-Quality

Growth Mindset vs Fixed Mindset
Welcome to SSCC Structure and Roles (Workbook)
Performance Feedback Training
Lesson 8 – Expectations for End of Day
Skills for a Healthy Life
Practical tools for conflict resolution
I will understand why people create government.
Don’t Let Work Be a Toxic Waste Zone
Brand promise guarantee
I understand it is important to keep going when something is tricky
Principles & ideas for improving project Management
Presentation transcript:

ACT AS A TEAM WITH CUSTOMER HOW TO BUILD THE CUSTOMER TRUST & LESSONS LEARNED

2 CONFIDENTIAL ExperienceAnalysisResult

3 CONFIDENTIAL WHO WE ARE Eugene Bobovik | Software Testing Team Leader Siarhei Kizer | Lead Software Engineer Dzmitry Shyshko | Senior Software Testing Engineer

4 CONFIDENTIAL UNCLEAR / INVISIBLE WORK AND PROCESSES OF MAKING DECISIONS Hard to organize effective process project-wide Huge informational lack Hard to ensure appropriate quality Hard to do planning and manage risks

5 CONFIDENTIAL UNCLEAR / INVISIBLE WORK AND PROCESSES OF MAKING DECISIONS Ways to deal with this: Collaborate with other teams Learn client’s business by yourself, suggest ideas Try brainstorming together Create knowledge base, suggest or improve processes Keep entire team informed about everything*

6 CONFIDENTIAL PRACTICE: INTENSIVE DEVELOPMENT APPROACH

7 CONFIDENTIAL TOO FORMAL OR COLD RELATIONS WITH CUSTOMER Hard to propose anything Even small mistake can grow into huge problem Team is under pressure

8 CONFIDENTIAL TOO FORMAL OR COLD RELATIONS WITH CUSTOMER What can we do? Be interested in client’s product Never try to hide or justify your mistake Accent on achievements and positive stuff Make every team member closer to client Do Demos

9 CONFIDENTIAL INITIATIVE Do not wait – ACT! Become an expert Insist, but keep the distance. Do not walk the line Solve customer problems, but do not create new

10 CONFIDENTIAL QA vs DEV EPAM vs CUSTOMER

11 CONFIDENTIAL COMPETITION WITH NON-EPAM TEAMS What makes us different: Rank and positioning Countries/Companies and contracts Social Goals Distance and timezones

12 CONFIDENTIAL COMPETITION WITH NON-EPAM TEAMS Focus on competition, not on product No knowledge sharing Pressure and rush Much time on issues resolving

13 CONFIDENTIAL COMPETITION WITH NON-EPAM TEAMS Let’s be mature: Make process that is clear and comfortable for everyone Share information and discuss things with non-EPAM teams Discuss improvements and issues Be positive!

14 CONFIDENTIAL UNCLEAR UNDERSTANDING OF CUSTOMER’S BUSINESS Team doesn’t know what they are working on: the idea that can turn motivation and proactivity is out there. Too many obvious / annoying questions to client Bad / No exploratory testing Difficult or impossible to suggest improvements or new ideas

15 CONFIDENTIAL UNCLEAR UNDERSTANDING OF CUSTOMER’S BUSINESS How to behave: Gather info. Ask questions! Never stop digging. Explain to client why you need this information. Represent examples of how it can make result better. Show achievements Be persistent. Never give up!

16 CONFIDENTIAL PRODUCTION ISSUES How it happens: We missed it Customer team missed it Customer has cancelled bug which reproduced on the production Another part of distributed team has missed it Maintenance issues

17 CONFIDENTIAL PRODUCTION ISSUES Rules: Do not blame anyone Do not lie Try to help Find evidences React quick

18 CONFIDENTIAL DOCUMENTATION CHAOS Hard to track Hard for newcomers Customer dependent on EPAM High risks

19 CONFIDENTIAL DOCUMENTATION CHAOS How to resolve: Centralize information storage Document environments and credentials Document Installation steps Have comments in code

20 CONFIDENTIAL TRUST CUSTOMER BUT DOUBLE-CHECK…

21 CONFIDENTIAL THE HUMAN FACTOR Rules: Be polite Don’t blame anyone Try not to hurt anyone Use interrogative position

22 CONFIDENTIAL CUSTOMER SHOULD KNOW HEROES! Team is motivated Easy to propose new ideas and add members Customer treats you as a partner

23 CONFIDENTIAL LET’S SUM-UP MAIN POINTS Let customer know that we are interested in their success Show that we can react really fast and effective Show why it is important to have us involved in their business: do something yourself and show something extraordinary Propose effective process or improvements targeted to make work more collaborated and transparent Explain the necessity of proposals

24 CONFIDENTIAL AS A RESULT YOU WILL GET Great collaboration of distributed teams Deep involvement and confidence of every member Full picture of the project value, internal or external limitations Satisfied team and customer Product development service instead of coding and testing

25 CONFIDENTIAL Keep the customer safe Make customer feel confident Keep customer involved