Agile bioinf

5,957 views

Published on

Introduction to scrum, lecture at the "Programming for Evolutionary Biology" workshop in Leipzig 2013.

http://evop.bioinf.uni-leipzig.de/

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,957
On SlideShare
0
From Embeds
0
Number of Embeds
4,976
Actions
Shares
0
Downloads
7
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Agile bioinf

  1. 1. Agile Bioinformatics
  2. 2. Why do research projects fail?
  3. 3. Why do research projects fail? (in programming)● Time wasted using wrong tools / cleaning bad data / etc..● Insufficient programming skills● Objectives not defined clearly / bad planning
  4. 4. Why do research projects fail? (in programming)● Time wasted using wrong tools / cleaning bad data / etc.. ask for help● Insufficient programming skills practice● Objectives not defined clearly / bad planning
  5. 5. Why do research projects fail? (in programming)● Time wasted using wrong tools / cleaning bad data / etc.. ask for help● Insufficient programming skills practice● Objectives not defined clearly / bad planning
  6. 6. Example: last years students project● Day 1: Lets do a project to analyze a dataset of Alternative Splicing expression
  7. 7. Example: last years students project● Day 1: Lets do a project to analyze a dataset of Alternative Splicing expression● Day 3: Working on five different projects at once
  8. 8. Example: PhD thesis● Day 1: professor explains great idea of PhD thesis
  9. 9. Example: PhD thesis● Day 1: professor explains great idea of PhD thesis● After 3 years: student working on a completely different project
  10. 10. Planning and Programming● Planning is the most important part in programming● If your objective are not clear, youll waste time
  11. 11. Planning is difficult, because objectives change!● Objectives always change over time – New priorities – New ideas – Somebody else published it – etc..
  12. 12. Planning is difficult, because objectives change!● Objectives always change over time – New priorities – New ideas – Somebody else published it – Etc..● Whats the solution?
  13. 13. Scrum● Scrum is an approach to software programming
  14. 14. Scrum● Scrum is an approach to software programming● Its a set of guidelines to how to organize your work: – How to define the objectives? – How frequently objectives must be re-stated? – How to organize daily work?
  15. 15. Scrum● Scrum is an approach to software programming● Its a set of guidelines to how to organize your work: – How to define the objectives? – How frequently objectives must be re-stated? – How to organize daily work?● Guidelines, not rules
  16. 16. The scrum “sprint”● The basic of scrum is to split the work into “sprints” of 2-4 weeks each
  17. 17. The scrum “sprint”● The basic of scrum is to split the work into “sprints” of 2-4 weeks each – Every 2-4 weeks, a meeting to redefine the objectives, and plan how to obtain them – Short daily meetings to check that everything is ok – A feedback meeting at the end, to discuss what went well or not
  18. 18. The planning meeting● A planning meeting is made every 2-3 weeks (beginning of the “sprint”)● Tasks: – Define main objectives – Divide work into single tasks
  19. 19. The planning meeting● A planning meeting is made every 2-3 weeks (beginning of the “sprint”)● Tasks: – Define main objectives – Divide work into single tasks http://blogs.microsoft.co.il/blogs/kolbis/
  20. 20. Planning table (post-its) Source of the image: wikipedia
  21. 21. The “post-it” rule ● Ideally, a task can be decribed in paper of the size of a “Post-it” ● If you cant explain it in a Post-it, then split it into two tasks
  22. 22. Objectives table(sorry – Ill put this online when I submitted the paper)
  23. 23. Daily meeting● 15 minutes meetings, every day in the morning● Each participant explains: – What have you accomplished yesterday? – What are you going to do today? – Are there any impediments / stumbling blocks?
  24. 24. Daily planning table(sorry – Ill put this online when I submitted the paper)
  25. 25. Daily Meeting example Barcelona runroom http://www.runroom.com/
  26. 26. Daily Meeting example Barcelona runroom http://www.runroom.com/
  27. 27. Daily meetings must be short!● The daily meeting must be necessarily not longer than 15 minutes● Anything that requires more than 15 minutes, should be discussed later
  28. 28. Never work more than 8 hours!● The day should be planned for 8 hours of work● If you consistently work more than 8 hours each day, you are not planning yourself well
  29. 29. Retrospective Meeting● At the end of each sprint (2-3 weeks) – What has been accomplished? – What has gone wrong? – What can be improved?
  30. 30. Retrospective table Image source: www.it-zynergy.com
  31. 31. Retrospective Meeting● At the end of each sprint (2-3 weeks) – What has been accomplished? – What has gone wrong? – What can be improved?● Tip: take a few days of “rest” after a sprint
  32. 32. Scrum - resume● Split your work into “sprints”, defining objectives that can be completed in 2-3 weeks – One planning meeting at the beginning – 15 minutes meetings every day – Feedback meeting at the end
  33. 33. Scrum - resume● Split your work into “sprints”, defining objectives that can be completed in 2-3 weeks – One planning meeting at the beginning – 15 minutes meetings every day – Feedback meeting at the end● These are guidelines, not rules
  34. 34. Example scrum calendar Image source: http://rocketninesolutions.com
  35. 35. How to know more?● Agile Barcelona – http://agile-barcelona.org/● Barcelona gamestorming grou – http://www.meetup.com/gamestorming-barcelona/● Look for the “Agile Programming” group in your city● Kane D, “Introducing Agile Development in Bioinformatics”, 2003

×