Skip to main content

Do it in small pieces

In a Agile project when we plan the work for the project, we split it in small pieces, a.k.a. User Stories. Then in the begging of the project we prioritize the small pieces in order to do first the most important pieces ("how" to prioritize is a subject to another post).
But all of this doesn't matter if the team decide to work in all the story at once.

The whole idea of breaking down the work and prioritize it, is to be able to keep delivering some business value along the development time. And more than that is a way to follow up the project progress.

Suppose that we have a project that will have 1 week iterations. In the first day of the 1º iteration the project board was with this status:

Stories                          In Dev                         In Tests                 Done
1                                       X
2                                       X
3                                       X
4
5
6
7

In the second day the developer Fulanom who was developing the Storie 2, decided to start coding a little piece of Storie 5 because the code was very similar to the Storie 2 code, just changing some parameters...

So in the second day the Project Board was:


Stories                          In Dev                         In Tests                 Done
1                                       X
2                                       X
3                                       X
4
5                                       X
6
7

All the others DEVs had the same ideia, what bring us to the following scenario:
Stories                          In Dev                         In Tests                 Done
1                                       X
2                                       X
3                                       X
4                                       X
5                                       X
6                                       X
7                                       X

This is bad, because now we have a Atomic Commit to the iteration, where or we delivery all the stories or we don't delivery any Story!
The idea behind the creating story, prioritizing,  is to not follow the Waterfall pattern of Atomic Projects.
Although sometimes from a coding perspective makes sense to code a new story instead of testing the coded story, this is not a great deal. As in the end you still have to test both stories. And as a test infected I'm sure that the surprises will arise during the tests. 

Comments

Popular posts from this blog

Page Object Pattern + WebDriver + Spring

During the last week I had start creating a test suite for a existing web-application which my team is currently working on. So now is good time to share some experience: The application A normal old java web application: Java 1.4, Struts 1.1, EJB 2.1, JDBC to persist the data and the anemic design (VO+BO+DAO) but I will talk about in another post... Page Object Pattern To map the web page's components inside the test code I used the page object pattern. This patterns helped me to eliminate duplicated code to access web-page's components. Basically it consists of classes that maps web-pages, so that if you want to fill a login form from your test classes instead of doing this: @Test public void someTest() throws Exception { WebElement userNameField = driver.findElement(By.name("j_username")); userNameField.sendKeys(username); WebElement passwordField = driver.findElement(By.name("j_password")); passwordField

Thunderbird with Microsoft OWA in Ubuntu 11.10

So, you as I are tired of Evolution's problems in Ubuntu 11.10 ? Move on to Thunderbird... To have it working with Microsoft OWA following the these steps: Install DavMail Download and install  DavMail . It will act as a proxy between Thunderbird and your Microsoft webmail. Configure DavMail Some tips:  Exchange 2003: https://mail.company.com/exchange/ Exchange 2007 Webdav mode: https://mail.company.com/owa/ Exchange 2007 EWS mode: https://mail.company.com/owa/ Exchange 2010 EWS mode: https://mail.company.com/owa/ Exchange 2010 EWS mode with unsupported authentication form e.g. Windows Live login:https://mail.company.com/ews/exchange.asmx In my case as I'm behind a proxy I had to mark the option "Use system proxy settings" in the Proxy tab: Click save then you should see a message in your system tray, saying that DavMail is correctly configured. Configuring Thunderbird In Thunderbird main window click menu Fil

How to avoid losing a unused terminal command line

This morning I got a great tip... I typed a command in my terminal but I wanted to run another command before executing the line that I just typed without loosing the information in the current line. For instance: I typed in my terminal the command: git commit -am "Unit test for scenarios A, B and C" But I was not sure if I was committing just the scenarios A, B and C that I have changed, I would like to run a git diff before committing but also without losing my committing message... Then my friend Duck told me to put a # in the begging of the line and...  voilà! # git commit -am "Unit test for scenarios A, B and C" It transform the line in a comment, so that I could hit enter without executing the commit and that line went to my history so that I could recovery it. Thanks Duck.