Throughout the years how teams worked has changed. There was a time when one person was responsible for all tasks, project management, business analysis, development and quality assurance and implementation. Then there was a swing to individual roles for each. Now, organizations are realizing the best approach is somewhere in between. Teams have to come together and determine what is necessary to reach their goals and determine who on the team is best to do the work. This is easier said than done. This presentation will discuss the differences, in skills and tasks, which separate the team roles and discuss specific strategies for building a strong partnership between all team members.

1. The Project Team –
One Big Happy
Family
Kupe Kupersmith, CBAP
President, B2T Training

2. Tweeting Today?
@Kupe
@B2T_Training
#baot
#pmot
#IIBA
#PMI

3. Agenda
• Why aren’t we one happy family?
• Where to focus your attention
• Guiding a Collaborative Relationship

4. Why aren’t we one happy family?
• Family fighting
Why aren’t we one happy
family?

5. The Five Dysfunctions of a Team

6. Performance Based on Individual
• Companies create titles and job description
• Various Bodies of Knowledge for roles
– PMBOK
– BABOK
– Etc.
• General attitude of people wanting to work within
a particular job description
• Titles Overlap
– PM/BA
– BA/QA

7. Who Cares What the BOKs Say?
• They are not bibles for titles
• There great guides for the work that has to be
done and competencies companies need to
achieve their goals

8. Teams are Built on Roles
Lead Business
Analyst
Sr. Business
Analyst
Development
Lead Sr.
Developer
Sr.
Developer
Architect
Project
Manager
Test Lead
QA
Analyst
UX Analyst

9. Room for Assumptions
There are gaps in work:
I thought
you were
doing it...
I thought
you were...

10. Room for Assumptions
Both groups are doing the same work:
I thought
I was
doing it...
I thought
I was...

11. Build One Based on Skills
Analysis Development
Testing UX

12. Build One Based on Skills
Traditional
Vision
Identify Needs
Facilitation
Process Knowledge
Analyze Impacts
Motivate the Team
Coding
Testing
Metrics
Agile
Vision
Identify Needs
Facilitation
Process Knowledge
Analyze Impacts
Motivate the Team
Coding
Testing
Metrics

13. Guiding a Collaborative Relationship

14. Self Assessment
• Understand your role within your organization
– What are your strongest skills?
– What are your areas for improvement?
• What tasks do you most enjoy?

15. Guideline to Better Working Relationship
Agenda
1. Get to know each other
2. Discuss project characteristics
3. Discuss the team members needs
4. Get clarity on project
outcomes

16. 1. Get to Know Each Other

17. Three Things in Common

18. 2. Discuss Project Characteristics
Project Objectives Measureable?
Success criteria
defined? Alignment with corporate strategy?
1.  Yes  No  Yes  No  Yes  No  Unknown
2.  Yes  No  Yes  No  Yes  No  Unknown
3.  Yes  No  Yes  No  Yes  No  Unknown
Stakeholder Name/Group Name Department or Organization Physical Location
1.
2.
3.
4.
5.
Outside Organizations Involved
1.
2.
3.
Key Requirements Deliverables (if known)
Existing systems that may be
impacted (interfaces)
1.
2.
3.

19. 3. Discuss Team Member Needs
• What Decisions does each team member need
to make?
• What information/help do you need to do your
job?
• What information do your team members need
from you to do their jobs.

20. What it Takes to Make a Decision
• What’s being decided?
• Who decides?
– One person
– Two or More
• What information do they need?
– Input to help decide
– Impact to evaluate options
• Where will the information come
from, or from whom?
The criteria for making decisions:
Break it down

21. 4. Get Clarity on Project Outcomes
• Project scope definition
–Project statement of purpose
–Project objectives
–Project business risks
• What does success look like
• Stakeholder relationships and communication
• Quality: plan for reviews of requirements,
designs & plans

22. Instill a Feedback System
1. Ask for Feedback
2. Be Appreciative
3. Implement Feedback
4. Provide Feedback on Feedback

23. It’s About Responsibilities
• Someone needs to take responsibility for tasks
• Collaboration is a must
• People do stuff they are good at and like
– You can use the guides to expand your skills
• How does your
company outline
roles…where do
you need
improvement

24. Never Say…It’s Not My Job

25. Who’s the Boss?
• Someone needs to take the lead
• Everyone should take the lead

26. Multi-tasking: Be careful
• Multi-tasking is not effective.
• People do not multi-task. They switch rapidly
between areas of focus.
Let’s Do an Exercise

27. What did you learn?

28. Final Thoughts
• Focus on the work, not the title
• Teams need to collaborate to come up with the
best approach
• Think in terms of making your
team members job easier

29. Stay Connected
• Questions for Kupe?
kupe@b2ttraining.com
• Connect with Kupe!
linkedin.com/in/kupetheba
• Follow us!
twitter.com/B2T_Training
twitter.com/Kupe
• Like us!
B2T Training Page