• Save
Scrum in Skype mobile software development - Challenges & Lessons learned @ MoMo Tallinn 06.06.11
Upcoming SlideShare
Loading in...5
×
 

Scrum in Skype mobile software development - Challenges & Lessons learned @ MoMo Tallinn 06.06.11

on

  • 2,542 views

Scrum in Skype mobile software development - Challenges & Lessons learned

Scrum in Skype mobile software development - Challenges & Lessons learned
Ervins Grinfelds
Skype
@ Mobile Monday Estonia "Mobile Development requires Agile approach?", Tallinn 06.06.11

Statistics

Views

Total Views
2,542
Views on SlideShare
1,738
Embed Views
804

Actions

Likes
1
Downloads
0
Comments
0

13 Embeds 804

http://www.momoestonia.com 423
http://www.mobilemonday.net 336
http://feeds.feedburner.com 15
http://planet.cs.ut.ee 11
url_unknown 5
http://translate.googleusercontent.com 3
http://mobilemonday.com 3
http://vm-202-167-238-75.advantage24.jp 2
http://repullulescent16.rssing.com 2
http://ww.mobilemonday.net 1
http://www.mobilemonday.com 1
http://ats.cs.ut.ee 1
http://www.google.ie 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Scrum in Skype mobile software development - Challenges & Lessons learned @ MoMo Tallinn 06.06.11 Scrum in Skype mobile software development - Challenges & Lessons learned @ MoMo Tallinn 06.06.11 Presentation Transcript

  • Scrum in Skype mobile software development - Challenges & Lessons learned
    Ervins Grinfelds
    Product Engineering Manager – Skype
    ervins.grinfelds@skype.net
  • Android for operators & OEMs
    • Operators – Verizon (US) , KDDI (Japan), Hutchison (UK, Ireland, Australia)
    • OEMs – HTC, Samsung, LG, Sharp, Sony Ericsson, Motorola
  • BlackBerry for operators & OEMs
    • Operators – Verizon (US) , Hutchison (UK, Ireland, Australia)
    • OEMs – RIM
  • Java ME for Operators & OEMs
    • Operators – Hutchison (UK, Ireland, Australia)
    • OEMs – Nokia, Sony Ericsson, ZTE, LG, Samsung
  • Transition to Scrum
    • Quick transition
    • Trainings/workshops
    • Teams started to work in Agile Scrum in OCT 2010
    • Working in Scrum for more than 7 months
  • Getting complexity points accurate
    • Complexity points are key to successful velocity calculation
    • Inaccurate velocity will prevent to execute effectively and in most cases will result in failed sprint
    Lessons learned
    • Getting very clear baseline (eg. what is complexity for 3 points)
    • Discuss until it’s understood by every team member
    • Refer to baseline estimations as much as possible.
  • Urgent/unplanned requests from Operators or OEMs
    • We must remain flexible & respond quickly to critical operator/OEM requests – even if outside of Sprint commitment.
    Lessons learned
    • Mandatory content – features/bug fixes that are mandatory for successful sprint. Typically ~ 60% of velocity.
    • Optional content – lower priority tasks
    • If unplanned request comes in, part or all optional content is replaced by new requests.
    • If no unplanned request – team delivers both – mandatory and optional content.
  • Getting burn down chart to work
    • Burndown - visibility of sprint progress
    Lessons learned.
    • Break down as much as possible
    • smaller tasks
    • Continuous integration is mandatory
    • Nightly builds
    • Daily automated regression tests & reports
    • Daily manual verification of changes
  • Definition of done – when to close sprint task
    • “Done” – state when sprint task can be closed (when it reflects on brundown chart)
    Lessons learned.
    • Done may vary between teams
    • Discuss, define & communicate definition of done as clear as possible until fully understood by team.
    • In Android, BlackBerry, Java ME task is done when:
    • Development complete
    • Code review by peers complete
    • Regression tests successful
    • Functional QA verification successful
    • Test cases & documentation (if applicable) changed.
  • Summary
    • Visibility
    • Efficiency
    • Flexibility
    • Discipline
    • Quality
  • Thank You!
    Ervins Grinfelds
    Product Engineering Manager – Skype
    ervins.grinfelds@skype.net