First Time in Team Project? Read this - extra: Agile Methodology, Simplified

What is Agile?

Imagine you're building a Lego castle with friends. Instead of planning every brick and step beforehand, you build a bit at a time. Every few days, you review the castle, see what’s working, and adjust based on what you and your friends like or dislike. This flexibility allows you to easily incorporate new ideas and fix things that aren’t working as planned.

Agile works similarly for software development. It’s a method where teams create software in small, manageable parts called "sprints," each lasting a week or two. During each sprint, the team works on a small piece of the project, reviews it, and adjusts it based on feedback before moving on to the next piece. This iterative approach helps teams stay adaptable and responsive to changes.

Principles of Agile:

• Customer Satisfaction: Deliver valuable software early and continuously.
• Welcome Change: Embrace changing requirements, even late in development.
• Frequent Delivery: Deliver working software frequently, with a preference for shorter timescales.
• Collaboration: Daily collaboration between business people and developers.
• Motivated Individuals: Build projects around motivated individuals and trust them to get the job done.
• Face-to-face communication: The most efficient and effective method of conveying information.
• Working Software: The primary measure of progress.
• Sustainable Development: Maintain a constant pace indefinitely.
• Technical Excellence: Pay continuous attention to technical excellence and good design.
• Simplicity: The art of maximizing the amount of work not done is essential.

Agile Team Structure and Roles

In Agile, teams function like a group of superheroes, each with a unique role but working towards the same goal. Here are the key roles in an Agile team:

1. UX Researcher:

- Role: Investigates user needs and behaviors through interviews and feedback.

- Goal: Ensure the software is user-friendly and meets user needs.

2. Product Manager (PM):

- Role: Defines the software’s features and direction, aligning it with business goals.

- Goal: Deliver a product that satisfies user needs and business objectives.

3. Product Designer/UI-UX Designer:

- Role: Designs the visual and interactive aspects of the software.

- Goal: Create an attractive and intuitive user interface.

4. Backend Software Engineer:

- Role: Develops and maintains the server-side components and databases.

- Goal: Ensure the backend operates smoothly and handles data effectively.

5. Frontend Software Engineer:

- Role: Builds the client-side components that users interact with.

- Goal: Ensure the interface is user-friendly and integrates well with the backend.

6. Fullstack Software Engineer:

- Role: Handles both frontend and backend development.

- Goal: Build and maintain the entire application from start to finish.

In Agile, team members collaborate and adapt their approach based on continuous feedback, rather than following a rigid plan. This flexibility leads to better software that meets user needs more effectively.

Team Activity: First Team Meeting

To ensure your first team meeting is productive, follow this agenda:

1. Introductions:

- Share names, reasons for joining, mission statements, and individual strengths.

2. Discuss Problem Statements:

- Each member presents problems they want to address. Select one that’s technology-solvable and clearly defined.

3. Define Team Roles:

- Assign responsibilities based on team members' skills and interests.

4. Plan Research:

- Decide what information is needed and how to gather it.

5. Brainstorming Session:

- Generate ideas for the problem statement and potential solutions.

6. Setting Goals:

- Define clear, measurable goals for the project to ensure alignment and focus.

7. Risk Assessment:

- Identify potential risks and discuss mitigation strategies.

8. Team Agreements:

- Establish ground rules and expectations for team communication and collaboration.

9. Schedule Next Meeting:

- Set a date and time for the next team meeting.

10. Record Questions and Comments:

- Document any questions or ideas that arise.

11. Assign Action Items:

- Ensure each member knows their tasks before the next meeting.

12. Choose a Team Name:

- Select a fun and meaningful name for your team.

13. Mini Retrospective:

- Briefly discuss what went well, what didn’t, and how to improve for next time.

14. Wrap-Up:

- Conclude the meeting and confirm the next steps.

Before the Next Meeting, Ensure:

- Meeting date and time.

- Team name.

- Agreed-upon problem statement.

- Assigned team roles and action items.

- Next meeting schedule.

Outstanding Teammates

• Essential Skills:

- Dependability

- Flexibility

- Problem-solving

- Communication

• 7 C’s of Communication:

- Clear

- Concise

- Concrete

- Correct

- Coherent

- Complete

- Courteous

• Proactive Communication:

- Anticipate needs and provide updates in advance.

• Listening:

- Avoid interruptions, stay attentive, restate, and confirm understanding.

• Consensus Building:

- Understand stakeholders’ views, agree on problems, brainstorm solutions, and create a space for feedback.

• Giving Feedback:

- Use micro-yes questions, be specific and objective, show impact, and end with a question.

• Opportunity Identification:

- Process: Define problems, ask the right questions, conduct web research, understand the audience, use user stories, illustrate problems, and consider technology.

Conflict Management Approaches

Conflict in Teams:

- Conflict is a natural part of teamwork and can lead to growth and better decision-making when managed well.

Thomas Kilmann Conflict Model:

• -Dimensions:

- Assertiveness: Willingness to assert one's needs and desires.

- Cooperativeness: Willingness to work together to achieve a mutual goal.

- Conflict Management Methods:

- Collaboration (High Assertiveness, High Cooperativeness): Working together to find a mutually beneficial solution.

- Competition (High Assertiveness, Low Cooperativeness): Competing to achieve personal goals, useful for motivating performance.

- Accommodation (Low Assertiveness, High Cooperativeness): Prioritizing harmony and others’ needs, ideal for minor issues.

- Avoidance (Low Assertiveness, Low Cooperativeness): Steering clear of conflicts, suitable for trivial matters.

- Compromise (Medium Assertiveness and Cooperativeness): Finding a middle ground where both parties make concessions.

Conflict Management Tips:

1. Practice Active Listening:

- Focus on understanding the other person’s perspective, paraphrase their points, and ensure clarity.

2. Search for Smart Tradeoffs:

- Identify what the other party values and make concessions on those points. In return, ask for concessions on what matters most to you.

Scenario Example:

Situation:

- Two teams, A and B, with different opinions and leadership styles are merged, leading to conflict between leads Aya and Beza.

Resolution:

- Recognizing the benefits of collaboration (high assertiveness and cooperativeness), Beza steps down, allowing Aya to lead. This change facilitates a more collaborative environment, helping the team work together effectively.

Summary:

• Agile is a flexible and iterative approach to software development that emphasizes collaboration, customer feedback, and rapid delivery.
• Roles in an Agile team each contribute uniquely to the project, requiring close collaboration and clear communication.
• Effective Team Meetings set the stage for successful collaboration and project management.
• Outstanding Teammates possess a mix of technical skills and personal qualities that enhance team dynamics.
• Conflict Management involves various approaches and techniques to resolve issues constructively and maintain a positive working environment.

credits: ALX Profissional Foundation Week 5