Muhammed Emre PEKKAYA

Empowering Teams for the Best

Architectures, Requirements and Designs

About Me

•M. Emre PEKKAYA emre.pekkaya@tubitak.gov.tr

•Agile Coach and Technical Lead at Software Technologies Research

Institute

•Developing products with Agile frameworks, methods and practices for

about 10 years

•Background: Software Developer, Business Analyst, Product Owner,

Process Architect

•Certifications: Professional Scrum Product Owner I, Sun Certified Java

Programmer (SCJP)

Outline

•Characteristics of Self-Organizing Teams

•Clear Goal

•Clear Boundaries

•Decision-Making Policies

• Improving Team Members’ Competence

•Questions

Many Scrum Teams

•Do Scrum events

•Produce Scrum artifacts

•Have Scrum roles

A Few Scrum Teams

•Employ Agile principles

•Employ Scrum values

•Employ technical excellence

Agile Principles

1. Produce value early

2. Embrace change

3. Iterative Delivery

4. Daily business collaboration

5. Trust motivated team

6. Face-to-face conversation

7. Working software

8. Sustainable development

9. Technical excellence

10. Keep it simple

11. Self-Organizing Teams

12. Inspection and Adaptation

Characteristics of Self-Organizing Teams

Team

Trust and

Respect

Collaboration

Motivation

Stability

Cross-

Functional

Clear Goal

Clear Boundaries

Sprint Backlog and Sprint Goal

Definition of Ready

Good User Story

User

Story

Negotiable

Valuable

Estimatable Small

Enough

Testable

Independent

Agile Principles

1. Produce value early

2. Embrace change

3. Iterative Delivery

4. Daily business collaboration

5. Trust motivated team

6. Face-to-face conversation

7. Working software

8. Sustainable development

9. Technical excellence

10. Keep it simple

11. Self-Organizing Teams

12. Inspection and Adaptation

Scrum Values

Definition of Done

Self-Assignment Rules

1. Decide which PBIs are implemented first in the beginning of the sprint

2. Don’t implement and also verify the same PBI

3. Select the closest PBI to the “Done” state

4. Correct your mistakes

5. Help teammate If there is no work to be done

Physical and Electronic Boards

Authority Levels

Key Decision Areas

1. Performance Rating

2. Software Development Model

3. People Hiring

4. Setting vacation days

5. Tool and Framework Selection

6. Daily Plan

7. Establishing coding standards

Authority Board

Improving Team Members’ Competence

•Self-Development

•Coaching

•Verification

•Tools

•Team Pressure

Summary

•Self-Organizing Teams have five characteristics

•Set a clear goal with qualified PBIs selected for a Sprint

•Set clear boundaries with Agile Principles, Scrum Values, Definition of

Done, Self-Assignment Rules and Decision-Making Policies

Thank you and Questions…