Iteration 2

Iteration 2

This is the second iteration of this project. Since the first iteration is completed, we did the iteration planning and started the user stories of the second iteration.

Date Duration: 27th March - 10th April

---

Meeting 1

Date: 27th March

We started iteration 2 and used Scrum Poker cards to determine the points that are to be given to the following user stories:

1. As a sales executive, I want to be able to order funnel elements so that customers can view funnel steps in sequence. (8 points)
2. As a sales executive, I want evaluators to be able to visit funnels I create so I have the opportunity to convert them to customers. (8 points)
3. As a web designer., I want to dynamically access the URL of the next page in the funnel through an API so I can use this to create links between pages. (20 points)
4. As an administrator, I should have access to all functionality available on FM. (5 points)
5. Set up Git on Linux server for faster deployment. (5 points)

We reviewed the previous code and managed to finish, user story 1, 2, 4 & 5 by today.

• User Story 1
• User Story 2
• User Story 3
• User Story 4
• User Story 5

User Story 4

As an administrator, I should have access to all functionality available on FM

Description: In this user story we had to assign roles to certain users. A user can be set to 3 types,an Administrator which has accessibility to all functions, a web Developer who can upload pages and add users, and a sales executive who can add/edit a campaign and also add a user.

User Story 5

Set up Git on Linux server

Description: User story 5 is done on a Linux server that Uniblue gave us access to. We also have a repository there for the final deployment of the product.

Meeting 2

Date: 2nd April

Today we discussed user story 3 (the last one that we have to do) and we started working on it. We also continued to work on the Jenkins, since now we are trying to install it on the server.

Meeting 3

Date: 3rd April

Today we installed Jenkins, and Git on the server so that we can manage everything directly from the server, since the product that we are making will run on the server. We installed Git on the server so that we could make pull requests on our repository directly from Github instead of transferring the file every time that a new version is created.

Jenkins is still giving us trouble since some ports on the server are closed and we need some configurations done on the Uniblue side.

Meeting 4

Date: 7th April

Today we finished up user story 3 while also started working on unit tests. We covered some unit tests and now we have some samples to continue work on. We checked that everything worked as it should, tried out everything (manual testing) and tweaked some little things in the code, like indentation, how to methods are under each other etc.

##Meeting 5

Date: 9th April Time: 12.30-2.45

We went to UniBlue to have a meeting with our Client,also we presented and showed him what we did during iteration 2 and how we tackled our User Stories. The client was pretty happy with the results so he started explaining to us the user stories and what was expected of us for Iteration 3.

##Meeting 6

Date: 10th April

Today we did the retrospective,we also gave points to our User Stories of the third iteration and discussed what we should be done. We also set up the Jenkins on the server. Since Jenkins is up and running we installed the appropriate plugins that we needed, like Git (to clone the repository from Github), Cobertura(for code coverage). We also installed python in Jenkins so that it could run python scripts (like the tests that we did, while also it can run the application).

In more detail:

• The workflow/what went well (as a team, work etc)

  • We finished all the user stories.
  • We managed to do some unit tests.
  • Good work distribution.
  • The user stories where given appropriate points.

• What could have been done better

  • Some user stories need to be read well so that higher points could be given.
  • Cover more unit tests so that the code coverage will be higher.

• Then we identified the flaws and made sure that they will be dealt with in the next iteration.

  • If the user story is found to be a bit complicated, higher points are to be given.
  • More unit tests are to be done so that better code coverage is done.