-
Notifications
You must be signed in to change notification settings - Fork 1
Milestone Report 1
Utkan Gezer edited this page Oct 21, 2016
·
5 revisions
- Ahmet Ercan Tekden
- Furkan Erdem Perşembe
- Esma Özelbaş
- Mehmet Utkan Gezer
- Kayahan Taşyaran
- Ezgi Tekdemir
- İsmail Enes Yılmaz
- İrem Zöğ
- Preparing a presentation including mock-ups and project plan to demonstrate to the customer.
- Meeting with customer and finalizing the project requirements and mock-ups before implementation.
- Discussing the project plan with customer.
- Deciding necessary development languages, frameworks and environments.
- Editing mock-ups
- Preparing for customer presentation
- Finalizing the project plan
- Reviewing the requirements
- Presentation is prepared.
- Mock-ups and project plan are finalized and discussed with customer.
- A requirement update is necessary.
- Android Studio will be used for android development.
- PyCharm will be used for web and back-end development.
- Customer thinks that newly voted posts will be shown on the top of the page. She also thinks that we can combine it with date and age it. If a user adds a new post, there is a chance for it to be seen.
- Customer demands that two different sorting algorithms, one using rating and the other using date, shown on separate table based on user’s choice.
- Customer thinks that pencil drawings are good idea.
- New requirement should be added for newly voted post shall be shown on the top of the page.
- All team members should know the details of the milestones. There should be milestones different than customer’s.
- Name: Unit Tests Milestone
- Date: 27th Oct 2016
- Objective: We are to prepare the unit tests for the individual units of our product by 27th of October, as per the customer request. We should come up with the documentation for the codes we write. And as always, update, keep up with the development we began.
- [Communication Plan] (Communication-Plan)
- Database Schema
- API Documentation
- [Description] (Project-Description)
- [Diagrams] (Diagrams)
- [Domain Analysis] (Domain-Analysis)
- [Features, Themes] (Features,-Themes)
- Mockups
- [Personas] (Personas)
- Plan
- Responsibility Assignment Matrix
- Requirements
- [Use Cases] (Use-Cases)
- [User Stories] (User-Stories)
- Peer Reviews
- Project Tutorial
- Repository Usage Manual
- [Test Plan] (Test-Plans)
- Ahmet Ercan Tekden
- Esma Özelbaş
- Ezgi Tekdemir
- Furkan Erdem Perşembe
- İsmail Enes Yılmaz
- İrem Zöğ
- Kayahan Taşyaran
- Mehmet Utkan Gezer
Preliminary Meetings:
- Meeting 1 (Feb 16)
- Meeting 2 (Feb 23)
- Meeting 3 (Mar 03)
- Meeting 4 (Mar 08)
- Meeting 5 (Mar 14)
- Meeting 6 (Mar 28)
- Customer Meeting 1 (Mar 31)
- Meeting 7 (Apr 05)
Meetings In-production:
- Meeting 8 (Sep 27)
- Meeting 9 (Oct 03)
- Meeting 10 (Oct 10)
- Git Meeting (Oct 14)
- Meeting 11 (Oct 17)
- Meeting 12 (Oct 24, expected)
- Meeting 13 (Oct 31)
- [Meeting 14 (Nov 7)] (Meeting-14)
- Meeting 15 (Nov 14)
- [Meeting 16 (Nov 21)] (Meeting-16)
- [Meeting 17 (Dec 5)] (Meeting-17)
- Meeting 18 (Dec 12)
- [Meeting 19 (Dec 19)] (Meeting-19)
within Sub-groups:
- Database Meeting (Oct 11)
- Android Meeting 1 (Oct 14)
- [Frontend Meeting 1 (Oct 14)](Frontend Meeting 1)
with Customer: