• Like
Teams and responsibilities
Upcoming SlideShare
Loading in...5
×

Teams and responsibilities

  • 486 views
Uploaded on

Presentation done at the W

Presentation done at the W

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
486
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
5
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ROLES IN AGILE TEAMSAmir Barylko - BDD MavenThought Inc.
  • 2. AMIR BARYLKO AGILE TEAMS ROLES & RESPONSIBILITIESAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 3. WHO AM I? • Architect • Developer • Mentor • Great cook • The one who’s entertaining you for the nextAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 4. RESOURCES • Email: amir@barylko.com • Twitter: @abarylko • Slides: http://orthocoders.com/presentations.htmlAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 5. LOOK MA!NO SLIDES
  • 6. ROLES IN CLASSIC TEAMSAmir Barylko - BDD MavenThought Inc.
  • 7. ROLES IN AGILE TEAMSAmir Barylko - BDD MavenThought Inc.
  • 8. HOW DO WE KNOW?Amir Barylko - BDD MavenThought Inc.
  • 9. SOME MAY CHANGEAmir Barylko - BDD MavenThought Inc.
  • 10. SOME MAY BE THE SAMEAmir Barylko - BDD MavenThought Inc.
  • 11. CAN’T CHANGE ALLAmir Barylko - BDD MavenThought Inc.
  • 12. ROLES Classic Better approach Micro Managing, Budget Collaborative, Team oriented, PM oriented isolate team to let them work Generate requirements BA documents Generate acceptance tests Generates design SA documents or diagrams Collaborative, focus on quality Dev Silo using TDD & BDDAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 13. ROLES II Classic Better approach Automated using acceptance tests and tools Manual, wait for testing to be done QA like Cucumber last Works with analysts to define the scenarios Provides Design, General Solution, Structure for Iteration 0 Architect Show powerpoint presentations Ver much about coding and being in the trenches Security Work with team while is getting standards or Review materials after is done implemented other std Authorize/review/centralize any Helps when needed, mostly with tuning, DBA operation to the database sharding, etc.... Funnel to any DB operationAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 14. WIN AS A TEAM • The goal is to produce value • while shortening the “lead time” • Helping other team members • should be a common practice • even if is not your usual roleAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 15. SUMMARY • The roles may change, however • the most important factor • is the attitude as a team • towards delivering value • and feel good about it :)Amir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.
  • 16. RESOURCES • Email: amir@barylko.com • Twitter: @abarylko • Slides: http://orthocoders.com/presentations.htmlAmir Barylko - Agile Teams, Roles and Responsibilities MavenThought Inc.