Question: Agile Programming For Bioinformaticians - Any Suggestions?
gravatar for Giovanni M Dall'Olio
10.6 years ago by
Barcelona, Spain
Giovanni M Dall'Olio420 wrote:

I am planning to prepare a talk for my workmates, to introduce them the basics of some agile programming methodology, which I think could give us good ideas to improve our working as a team.

My idea was to take inspiration from extreme programming and explain the rules I like the most: use of A7 cards to write tasks, release planning every 3 week, stand-up meeting every day, Move people around, unit tests first, pair programming (at least introduce the concept), collective ownership.

It is difficult for me to explain these rules as I don't have much direct experience with, apart for few exceptions, and it is even more difficult because I will have to explain them to people who are not comfortable with programming and with software engineering in general. However, I also think that I have to prepare this talk early and it will be much more difficult if I wait too much.

Do you have any experience with what I am talking about? Do you have any advice to give me, or can you recommend me a book or a practice that I could explain along with extreme programming?

general agile good team • 1.2k views
ADD COMMENTlink modified 10.6 years ago by User 82260 • written 10.6 years ago by Giovanni M Dall'Olio420
gravatar for Konrad
10.6 years ago by
Konrad20 wrote:

I would suggest to have a look at Scrum, too. Certain parts would help not only bioinformations. For example estimating the time expenditure of tasks and the resulting burn down charts can be really helpful to see if something is stuck especially when working together on bigger projects.The daily scrum reports helps to meditate why who is doing what and offers a platform to discuss problems.

ADD COMMENTlink written 10.6 years ago by Konrad20
gravatar for István Albert
10.6 years ago by
István Albert ♦♦ 310
University Park
István Albert ♦♦ 310 wrote:

I think the approach is unsuited for individuals who are not comfortable with programming in general. There is a long way to go until someone becomes confident in their abilities. Before that this approach is not only ineffective, it might be even be detrimental.

Instead what helps most is transparency. Everyone needs to write code in a source code repository that can be viewed, commented and verified. People should become familiar with testing, code coverage, and continuous integration.

Something to read: Mythical Man Month.

ADD COMMENTlink written 10.6 years ago by István Albert ♦♦ 310
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 1 users visited in the last hour