• The scope of the project was decided together with the team.

• Furkan2001 found a customer for the project.

• meteahmetyakar prepared the jira as shown below for the team to use.

  • Special issue types such as spike

    

  • Special fields

    

    

  • Seperate boards each department (Members can only see the department associated with them)

    

  • Setting up workflows and column settings, for example an issue in 'DONE', it cannot editable.

    

  • Defining groups

    

• meteahmetyakar prepared templates of the pages to be used in the meetings.

  • Customer Interview Template

    

  • Sprint Planning Meeting Template

    

  • Retrospective Template

    

• meteahmetyakar created the areas that the team would use when preparing documentation.

  • Prototypes Field

    

  • Requirements Field

    

  • Test Cases Field

    

  • Retrospectives, Sprint Planning Meetings, Customer Interview Fields

    

• Prototypes were prepared in Figma to show the customer the design and function of the project. Then they were presented to the customer and the project was started after the feedback received

• Web Side Prototype prepared by berke-yilmaz

  

• Mobile Side Prototype prepared by noktahesefe

  

• Furkan2001 did research on the domain and hosting service we would use and we purchased a domain that could meet our needs.

• After the preparing and the presentation we did our first sprint planning meeting and then we started the project.

  • PA Sprint 1

    

    • PA Sprint 1 Report

      

    • End of the PA Sprint 1 we made retrospective, we discussed our first sprint report (we knew it was terrible) and our problems

      

  This process continued regularly until the end of the project. We constantly made plans, worked hard, then discussed our mistakes and tried to improve ourselves.

  • PA Sprint 5

    

    • PA Sprint 5 Report

      

  At the end of PA Sprint 5, we were at a completely different point than where we started. We had made progress that we could be proud of.

160-page documentation prepared by the entire team by distributing tasks.

Content of documentation:

• User Stories and related scenarios
• User Requirements
• System Requirements
• Figma Prototypes
• Use Case Diagrams (Web Side, Mobile Side)
• Detailed Use Case Tables
• Backlogs
• Context Model
• Process Models
• UML Class Diagrams (Web Side, Mobile Side)
• Sequence Diagrams (Web Side, Mobile Side)
• Documented Test Cases (Web Side, Mobile Side)

project documentation