Skip to content

Iteration 1

Jump to bottom Edit New page
alastairchet edited this page Apr 16, 2014 · 13 revisions

Iteration 1

In this iteration we started the user stories that we planned with the customer.

Date duration: 10th March - 24th March

Meeting 1

Date: 10th March

Today we had the first meeting of our Iteration 1 and we did the Iteration Planning to see what we are going to do in this iteration and how we are going to divide things.

We used the Scrum Poker Planning Cards to assign points of working/planning time. The user stories with their appropriate given points are as follows (as they are currently):

  1. As a Uniblue employee, I should be required to log in to the funnel management admin interface so I am restricted to content I have rights for. (5 points)
  2. As a web designer, I need a location where I can store completed landing page templates for retrieval by FM. (8 points)
  3. As a web designer, I want to manage created landing page templates through the admin interface so they can be made available to sales executives. (5 points)
  4. As a sales executive, I want to be able to create a custom funnel so that I can use this to acquire new customers. (13 points)
  5. As a sales executive, I want to select landing page templates to add as possible new elements to a funnel. (8 points)
  6. As a sales executive, I want to be able to order funnel elements so that customers can view funnel steps in sequence. (8 points)
  7. 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. (5 points)
  8. 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. (8 points)

We also familiarized ourselves with the tools that we were going to use like PyCharm which is an IDE for developing Python applications.

Since the user stories where given to us already we started with the first two user stories. We finished them by the end of the day with the only exception of the Amazon S3 bucket for cloud storage.

Meeting 2

Date: 12th March

Today we discussed user story 3 which we had to do on Thursday, while also reviewed Monday's work.

To make the user interface more user friendly, we chose to use Twitter Bootstrap which is a front-end framework.

We are still trying to configure Jenkins, since it has some trouble on the server regarding python scripts.

Meeting 3

Date: 13th March

Today we started and finished user story 3 and started on user story 4. User story 3 was not hard to implement and did not take us a lot of time, but user story 4 took us a lot of time and encountered a bit of difficulties. We had to work on it also at home.

We took a lot of time in how we are going to present it, since there are a lot of different ideas on how to approach the design. We also found some difficulties in making it work correctly (hence the points given) but we managed to do it.

Meeting 4

Date: 17th March

We finished last few things of user story 4 and started working on user story 5 and 6. We managed to do user story 5 with some little extra things that we added (to make it more user friendly) and we also managed to finish user story 6.

Meeting 5

Date: 20th March

We met up to discuss the last user stories and reviewed the work that we did till now and re-arranged some things that we did not like.

We managed to finish user story 8 and were about to start user story 7. Since user story 8 we found some difficulties in connecting to Amazon S3 bucket we discussed in working on it at home.

Meeting 6

Date: 24th March

Today we reviewed the whole code and fixed some bugs that we had, like upload with no name or email etc.

Edited some minor things that needed to be done.

Meeting 7

Date: 26th March

Today we had the final meeting with our client. We showed the demo to our client and was pleased with the results. He wanted to change some things to make it better.

We also managed to connect with the Amazon S3 Bucket since they arranged some things on their side when we went to meet them.

Meeting 8

Date: 27th March

Today we did the retrospective and discussed on how to deal with them, so that in iteration 2 we do not encounter them again.

In more detail:

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

    • We finished all the user stories.
    • We managed with the new programming language well.
    • Good communication with the team

  • What could have been done better

    • Better point distribution to the user stories.
    • Better work distribution.
    • More unit tests

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

    • Distribute work better between team
    • Set up Jenkins appropriately and start making unit tests.
    • During the iteration planning, we shall be focusing and explaining exactly what each of the user
      stories needs to be done and then distribute the appropriate points.
Add a custom footer
Add a custom sidebar

Clone this wiki locally