Have you ever wondered what the best software team looks like? Are you aware of the different roles needed to accomplish the tasks and deliver a high-quality software product?
Whether you have no previous experience with software teams, or you have never outsourced these capabilities before, you'll find valuable insights on what you need to create your next best-seller software product.
Based on our experience of more than 200 projects successfully undertaken, you’ll learn on:
Key Factors of Effective Team Building
Project Scope
Team Size
Team Location
Software Dev Methodology
Communication
Defined Roles & Responsibilities
Real Case Study
Tips on the Team Creation Process
6. • Key factors of for an effective team building
◦ Project Scope
◦ Team Size
◦ Team Location
◦ Software Development Methodology
◦ Communication
◦ Defined roles & responsibilities
• Case study
• Q&A
Topics
9. Project Scope
We can identify 2 situations:
1
2
Clear Project Scope Definition
Unclear or Missing Project Scope Definition
10. Team Size
• Typical Scrum Team composition: 7-10 members
• If the team size increases, so does the number of
conflicts
• Split the team into subteams
11. Team Location
• Will my teams be distributed in several locations?
• How can they communicate effectively?
• What do I need to be able to work with teams in
multiple locations?
• How can you grant visibility to the team’s activities and
their progress?
12. Team Location
• Real-time, online collaboration tools
• Top talent is spread around the globe
• Flexible policies related to working from home
13. Software Development Methodology
• Is the company familiar with Agile
Methodologies?
• We’re already working with a given methodology.
Do we have to change it?
14. Software Development Methodology
• The methodology conditions and determines the
team composition.
• The team composition needs to adapt the reality
of the current teams and methodologies used by
the client.
15. Defined Roles and Responsibilities
• Choose the right people to be part of the team
• Appoint or elect one person to lead based on leadership qualities
• Building a team is a process that takes time but also saves time
• Classic roles that a company needs:
1. Scrum Master/Team lead.
2. SME.
3. Development Engineer.
4. UI/UX developer / Graphic Designer.
5. QA Engineer.
16. Communication
• Key to any successful team Building
• Might be affected by barriers like language and global
cultural differences
17. Real Case Study
1 Scrum Expert at the beginning of a project
18. 1
Near-Shore
(PM)
Amatista
(claims)
Diana
Sudeep
Ariel
Carolina
Lucas
Javier
M.D.
Juan Pablo
Cristian
Oro
(claims)
Ruben
Wade
Nestor
Francisco
Abel
Guillermo
Elina
Mariano
Diego
Zafiro
(claims)
Diana
Sree
Sebastian
Leandro
Evangelina
Miguel
Gonzalo
Fransisco
Nahuel
Esmeralda
(claims)
Ruben
Senthil
Ale
Javier
Guillermo
Jose
Santiago
Marta
Diego
Near-Shore
(Jose)
Scrum Expert at
the beginning of
a project
Julieta (Lead
QA/PM)
19. Real Case Study
2 Unclear or Missing Project Scope Definition
20. 2
Near-Shore
(PM)
Amatista
(claims)
Diana
Sudeep
Ariel
Carolina
Lucas
Javier
M.D.
Juan Pablo
Cristian
Oro
(claims)
Ruben
Wade
Nestor
Francisco
Abel
Guillermo
Elina
Mariano
Diego
Zafiro
(claims)
Diana
Sree
Sebastian
Leandro
Evangelina
Miguel
Gonzalo
Fransisco
Nahuel
Esmeralda
(claims)
Ruben
Senthil
Ale
Javier
Guillermo
Jose
Santiago
Marta
Diego
Near-Shore
(Jose)
Unclear or
Missing Project
Scope Definition
Julieta (Lead
QA/PM)
21. Tips/recommendations
• Clear Project Scope Definition
• Project Scope unclear or undefined: agree with the
client and make suggestions
• Typical Scrum Team composition of 7-10 members
• Avoid large teams
• Good management and communication
• Agreeing on a methodology
• Adaptability
22. Tips/recommendations
• Choose the right people
• Elect one person to lead the team
• Creating a team takes time but also saves it
• Communication is essential
• Meet the team face to face