javantura v2 - team forming with agile tips & tricks - roko roić

Post on 05-Jul-2015

665 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

In large or enterprise software development engagements, one man can not go where a team can. You’d think that putting a well balanced group of people on a project would end up to good teamwork? It is not as simple as that. But maybe it is simple after all, with some Agile and Lean tips and tricks. I will share my experience as a seasoned team manager (PM, PO, Team lead) as well as some formal research on the topic of “how to create a team”.

TRANSCRIPT

TEAM FORMING WITH AGILE TIPS&TRICKS

@RROIC

JAVA DEVELOPER AGILE CROATIA BOARD MEMBER MANAGING SOFWARE DELIVERY @KING ROCK CLIMBING WRITING A BOOK ON AGILE ROKO.ROIC@KING-ICT.HR

THE PROBLEM #1 NO SINGLE DEVELOPER CAN DELIVER LARGE PROJECTS IN REASONABLE TIME

THE SOLUTION FORM A TEAM OF PEOPLE TO DO THE JOB.

THE PROBLEM #2 FORMING A TEAM IS NOT EASY. A GROUP OF PEOPLE DOES NOT A TEAM MAKE.

THE SOLUTION IS NOT SIMPLE, BUT WITH A LITTLE HELP FROM LEAN AND AGILE…

BUT FIRST SOME THEORY…

TEAM DEFINITION

A TEAM COMPRISES A GROUP OF PEOPLE LINKED IN A COMMON PURPOSE. TEAM MEMBERS (1) OPERATE WITH A HIGH DEGREE OF INTERDEPENDENCE, (2) SHARE AUTHORITY AND RESPONSIBILITY FOR SELF-MANAGEMENT, (3) ARE ACCOUNTABLE FOR THE COLLECTIVE PERFORMANCE, AND (4) WORK TOWARD A COMMON GOAL AND SHARED REWARDS(S).

TEAM !DEFINITION

NOT (JUST) A GROUP OF PEOPLE WORKING TOGETHER. SHOULD CONSIST OF 3 OR MORE PEOPLE - 2 IS A PAIR. A SINGLE PERSON MAY CONTRIBUTE TO MORE THAN ONE PROJECT AT A TIME, BUT WILL RARELY CONSIDER THEMSELVES AS BELONGING TO MORE THAN ONE TEAM AT A TIME.

* BRUCE TUCKMAN, “Team development model” 1965.

CHARISMATIC LEADERSHIP

ORGANIC GROWTH

AGILE TIPS AND TRICKS

OFFICE SPACE

„The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”

SCRUM CEREMONIES

Sprint planning, Daily Scrum, Sprint Review and demo, Sprint Retrospective all take a form of face to face meetings

SELF ORGANISATION

„The best architectures, requirements, and designs emerge from self-organizing teams.”

ELIMINATING WASTE

„Simplicity --the art of maximizing the amount of work not done-- is essential.„

INDIVIDUAL MOTIVATION

„Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. „

REACHEABLE GOAL

„Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”

PROCESS TRANSPARENCY

Can team members influence how we achieve the goal? First they need to understand what we are doing.

CONTINUOUS IMPROVEMENT

Kudos to those who help the collective improve. Empover this process by formal and informal tools.

SERVANT LEADERSHIP

People like to be led, it gives them a sense of trust . But they need help as well.

STABLE TEAM

„Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.”

SLACK

Hyper utilization is a problem, but hyper productivity is also an issue. How can we form a team if they can barely manage a conversation due to lack of time?

Q&A ROKO.ROIC@KING-ICT.HR @RROIC

top related