Your SlideShare is downloading. ×
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Agile EE 2010
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile EE 2010

145

Published on

this is files from huddle

this is files from huddle

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
145
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
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. Alena Lavrinenko & Tanya Mezentseva
  • 2. Quick look on Agile methodologies:
    • Scrum is a framework for managing projects or, more generally, work. It is iterative and incremental, which means that it asks a team to work for a short period of time (a “sprint” or “iteration”) and then demonstrate real stuff (a product increment) that matters to the end-product at the end of each sprint.
    • Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted.
    • Kanban system is generally easy to understand, simple to visualize and comparatively easy to set-up. “Use one, make one” is the simplest form of this method.
  • 3. Distributed teams
    • Reasons to go distributed:
    • No local talent available
    • Customers elsewhere
    • Specific skills elsewhere
    • Round the clock team
    • Great people move
    • Invalid reasons:
    • Cheaper workforce
    • No office space
    • Desire to be “global”
  • 4. How to make work easier in DT
    • Respect each other
    • Be honest
    • Get to know your remote peers
    • Share bad and good things
    • STOP – managers here, subordinates there
    • STOP – meeting overdose
  • 5. Visualization
    • Which information needs to be shown?
  • 6. Type of charts
    • Sprint Burn down chart
    • Product burn down chart
    • Task board
    • Visual board
    • Domain chart
    • Challenge board
    • Territory chart
  • 7.  
  • 8. Product burn down chart Purpose : Product progress visibility Advantages : Immediate reflection of the real deadline Disadvantages : Immediate reflection of the real deadline Audience : Everybody Who likes it the most : High Management
  • 9. Task Board Purpose : Content visibility Advantages : Immediate understanding Disadvantages : Lack of overall visibility Audience : Everybody Who likes it the most : Scrum team Task Effort Owner
  • 10. Example
  • 11. Extreme task boards
  • 12.  
  • 13. Example
  • 14. Example
  • 15. Domain Chart
  • 16.  
  • 17. Challenge Board Purpose : Problem visibility Advantages : (Immediate) understanding what bothers the team Disadvantages : Sometimes you find out strange things about the team… Audience : Everybody Who likes it the most : Middle Management
    • Free drawing of the problems
    • The team does the drawing
  • 18. Summary
  • 19. Common problems in team working:
    • Misunderstanding
    • Lonely wolves
    • Problems reticence
  • 20. SOLUTION!
  • 21. Scrum Games! Break from the usual routine Have some fun Learning in a snap! More EFFICIENT
  • 22. Self empowerment
    • Split into pairs
    • One is the BOSS and one is the EMPLOYEE
    • The BOSS needs to walk the EMPLOYEE as many steps as s / he can using the words: left, right, backward, forward
    • Same requirement but the team is empowered
  • 23. Pushing 40
    • As the team count till 40 as fast as you can
    • No specific order is allowed
    • Only one team member says a number
    • Start from the beginning if you fail
  • 24. Team vs. individual
    • Form a circle
    • Choose one person on the other side
    • Round I: Exchange places with him
    • Round II: Now think is a group…
  • 25. 6 hats brainstorming
    • Each person in the table choose a hat
    • Make sure you have all the hats
    • Start debating about ideas
  • 26. Summary
    • Only cohesive team can be hyper productive team
    • Fun is prerequisite to creativity
    • Overtime is not 9 th hour but is the time in when you feel you do not want to work anymore
  • 27. THANKS !!!
    • QUESTIONS?

×