Skip to content

Project conclusion report

Hadas135 edited this page Jun 28, 2017 · 7 revisions

Table of Contents

Team values and spirit

Development process

Project and course reflection

👉 Main lessons from this project

👉 What worked well and what worked less good and what we will do differently next project

👉 Challenges we deal with

👉 Effect of risks management

👉 Guest lectures

👉 Which tools were helpful and which less

👉 Working in front of the client

👉 Future plans

Team values and spirit

As we described during the project, at the beginning our tean didn't work us a team and therefore our products were Stylized diffrently. According to that, our client was not pleased with the final products we had in the first iteration. We learned from this and at the second iteration we we already worked as a team and updated each other. at the beginning, teamwork was hard and we had to learn how to work as a team and afterwords our team work had improved and at the end we worked excellently together and the results are shown.

In general, we worked good as a team- we all worked together as co-workers on the project. All of us had the same interest- finishing the app in time, we made it and over come the hard times and risks while working on the project.

For example, after we finished designed all the pages and screens in our app, and meeting with the client, he wasn't happy (click here) and even changed some of his requests. Thanks to our good team work we manage the time well so that even though there was a delay, the application was ready on time.

Development process

When we started the process in iteration 0, we sat 4 development rounds- one for screens, 2 for the functionalities and the last one for check ups. Likewise, we shared the time equally between each iterations.

When we started the project, we worked slower than the expected because the workspace was unfamiliar to us and it took us some time to understand angular. Therefore, we divided the iteration so we gave longer time to the first two and less to the other two.

Afterwords, when we required in the end of the first iteration to change all the screens, the first iteration "slowly burned" and we had to change the plans for the other iterations according to it. Therefore, we decided that short iterations two would be fixing the screens, iteration three would be all the functionalities and iteration 4 would be check ups.

With that, because we worked so well on iteration three and we accomplish all our functionalities- and even added main admin (click here) who wasn't in the original planning- so we've done far more for one round. That's why we decided to combine iterations three and four, so we created iteration 3+4 with the main goals of- functionalities, the main admin and tests our product.

Project and course reflection

Main lessons from this project:

  1. Team work- as it's been describe here, we learned how to work correctly as a team. In the beginning there were some difficulties but thanks to the course we learned how to mange correctly as a team and focussing on our mutual goal, succeed. We had our disagreements as expected but in the end we over come them all and we were all happy. We are glad that in addition to professional experiences we have gained from the project, we also gain team work experience that is important to us neither the less.

  2. Working with the client- it's important neither the less of what we described above. Although in this project the client came to us with the idea and we haven't presented it to him and convinced him to invest in it, but we still gained experience in work in front of real clients. We learned in which constancy to meet with him, how to mange and how to stand with the changing requests of the client, and even changing them a little and adding stuff that hadn't been planned before.

  3. Accomplish- of course, we learned how to use angular. When we started the project, we didn't recognized with the workspace, and while progressing with the project we learned it better.

What worked well and what worked less good and what we will do differently next project:

You can see here, here and here.

Challenges we deal with:

As you can see here, the main challenge that we deal with was the changing requests from the client. Because of the changing requests a complete iteration was wasted and a huge gap was created between the goals we were supposed to achieve and the goals we actually achieved. Therefore, in the next iterations we had to invest a lot and run against time in order to narrow this gap.

In addition, we had to deal with the fact that everything was new to us - it's the first application we developing. We learned how to organise the work steps in right way and value the timing of everything, how to handle in front of the client, team work and even learning new language by ourselves.

Effect of risks management:

You can see here, here and here.

Risk management has led us to plan ahead and take action many times in order to reduce the chances that risk will indeed occur. We plan the time according to the most relevant risks, so that in the event that risk occurs, we will know how to handle it and adjust our time to treat it. Risk management helped us prepare for an expected future of the project and put us in proportion to the difficulties created during the project.

Guest lectures:

Guest lectures gave us mostly motivation through the all project, and different observations on all.

Which tools were helpful and which less:

We used managing versions in GitHub as we learned in the course, and etesting our product.

The tools that were lass helpful through the project were things like the blind typing that is less relevant to the project.

Working in front of the client:

As we wrote here in section 2, the work in front of the client was meaningful and helpful. At the end of each iteration, the customer received a kind of ready-made product and gave him reviews, which guided us more to his needs from the product and to the way he imagined the product. Sometimes working alongside the client was difficult, and in the first iterations, his reactions even led us to frustration. But finally, in the last two iterations, when we brought him a product that came closer to his requirements and surprised him when we brought him another layer in the app which he did not think about, we finally received good feedbacks and we began to feel the satisfaction of it.

Future plans:

As for now, we transforming the product to the client. It's possible that he might continue developing it, but not with us. We promised him that we would be available to any question he have, but he would need to contact with someone else that would do so for him.