Building the A-Team (Agile Team). What is Agile, Understanding what it means to be Agile, Agile terms, tools and principles.

1. The A - (Agile) Team
By
Bruce Lucas N.
Organizer, forLoopPH

2. A typical developer
• Creative mind
• Problems solving skills on the hour
• Doesn’t always fit in with corporate work
• DIY fired
• Likes team work but prefers to work alone.
• Always chased by deadlines
• Always loosing money
• Build once, support for life
• …..

3. The new paradigm…
Teamwork
Business minds Tech minds

4. What is Team?
a group of players forming one side in a
competitive game, to execute a task, etc

5. What is Agile?
A set of Values and Principles

6. What Agile is NOT
• Not a Framework
• Not a process
• Not a Software
• Not a Design language
• Not a specific way of Developing Software

7. Agile
Agile
Collection of
Beliefs
Used to make
Decisions
On how to
Develop Software

8. Agile simply gives you a foundation
for teams to make decisions
And
Agile practices keeps the team
organized.

9. Agile Manifesto – 68 words
over
Develop Software better by valuing items on the left side of the list than those on the right side
Individuals and interactions Processes and tools
Working Software Comprehensive Documentation
Customer collaboration Contract Negotiation
Responding to change Following a plan
Credit: Mark Shead

10. 12 Principles of Agile

11. 1.
Our highest priority is to satisfy the customer
through early and continuous deliver of
valuable software.

12. 2.
Welcome changing requirements,
even late in the development.
Agile processes harness change for the
customer’s competitive advantage.

13. 3.
Deliver working software more frequently,
from a couple of weeks to a couple of months,
with a preference to a shorter timescale.

14. 4.
Business people and developers must
work together daily throughout the project.

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

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

17. 7.
Working software is the primary
measure of progress

18. 8.
Agile processes support sustainable
development. The sponsors, developers
and users should be able to maintain a
constant pace indefinitely

19. 9.
Continuous attention to technical
excellence and good design enhances agility.

20. 10.
Simplicity – the act of maximizing
the amount of work not done is essential.

21. 11.
The best architecture, requirements
and designs emerge from self-organizing team.

22. 12.
At regular intervals, the team reflects
on how to become more effective,
then tunes and adjusts its behavior accordingly.

23. Agile Teams
Agile teams make decisions every day and those decisions have to be in
tune with the values and principles that works best for them.

24. Agile Practices
Agile practices can be different for different teams but it is more
centered on the
WHY of those practices
rather than the
WHAT kind of practice?

25. SCRUM VS KANBAN
Remember: Practices don’t make you agile.
STAND-UP VS SEAT-DOWN MEETINGS
Your PRINCIPLES and VALUES are what makes you agile.

26. Choosing practices that support your
principles and values.
That is how you build an Agile Team.

27. Agile terms?
• User Stories
• Epic
• SCRUM
• KANBAN
• Board
• List
• Cards
• Sprints
• Retrospective
• Continuous Integration
More…

28. User Stories
Following the Agile principle No 7.
Working software is the primary measure of progress.
A story template
--------------------------------
WHO - As a : [Type of user]
WHAT - I want to: [Type of action to perform]
WHY - So I can: [achieve this result]

29. Example of a clear User Stories
As a: Website Visitor
I want to: Subscribe to a mailing list for a product.
So I can: Receive email updates for the product.
As a: Admin User
I want to: Disable Users
So I can: Prevent unauthorized access to the software at any time.

30. A good story…
Reflect the understanding of the user’s
needs and expectations.
And supports our agile principles

31. Tools for Agile Teams
• JIRA
• Pivotal Tracker
• Trello
• Wrike
• Agilean
• Planbox
• Assembla
• Asana

32. The Emergency CEO Syndrome.
KILL

33. The thin line…
Freelancer Businessman
Build a career and earn a living… Build a company and earn a living…
More code…
You do the work…
less code…
People work for you…

35. Thank you
08036602512
brucelucas@olotusquare.co
www.olotusquare.co
forloopph@gmail.com
www.forloop.africa
Bruce Lucas N.
@brucealgorithm
08036602512