# data[].attributes.body
1) What did you do so far / between the current and the last Sprint meeting?

2) What issues or roadblocks did you identify and how did you identify them?

3) How are you going to deal with  the issues specifically to improve the working process

# data[].attributes.body
15/11/2021, 11.00-13.00
Teammeeting about planning, for the tasks that need to be done this week, see sprint #1. Everyone is present.

16/11/2021, 10.30-12.15
Seminar 3 Q&A part 1. Everyone is present.

22/11/2021, 10.30-12.15
Seminar 4. Everyone is present.

22/11/2021, 12.15-13.15
Teammeeting to see where we stand, if all tasks have been accomplished and what the distribution of tasks for the coming week will be. For the tasks that need to be done this week, see sprint #2. At the end, record sprint video #2. Everyone is present.

29/11/2021, 11.00-13.00
Teammeeting to see where we stand, if all tasks have been accomplished and what the distribution of tasks for the coming week will be. For the tasks that need to be done this week, see sprint #3. At the end, record sprint video #3. Everyone is present.

6/12/2021, 11.00-13.00
Teammeeting to see where we stand, if all tasks have been accomplished and what the distribution of tasks for the coming week will be. For the tasks that need to be done this week, see sprint #4. At the end, record sprint video #4. Everyone is present.

13/12/2021, 11.00-13.00
Team meeting to complete the project. Checking if everything is complete, what tasks still need to be performed and divide them. After this meeting we want to be able to start working on the final presentation and the final reflection report. Also see sprint #5. At the end, record sprint video #5. Everyone is present.

20/12/2021, 10.30-12.15
Final presentation, everyone is present.

# data[].attributes.body
Final goal
Redesign, with proper explanation and justification, the packing lay-out and/or increase the packing productivity, maximizing the packing throughout as much as possible.

Sub-goals to meet the final goal
- Desribe the type of warehouse design approach of CEVA
- Costs & benefits analysis current situation
- Make visible the flow in the current situation by using appropriate charts
- Come up with a new lay-out and/or new way of working that maximizes the packing throughout as much as possible.
- Describe the new lay-out and new way of working in detail
- Explain the choice of the new lay-out format
- Costs & benefits analysis new situation
- Make visible the flow in the new situation by using appropriate charts
- Reflect critically on a weekly basis on how we work and our outcomes.

# data[].attributes.body
Core tasks
Complete the Padlet and record sprint video. An important part of the Padlet is planning, which is essential for this project to run smoothly.

Sub-tasks
- Description of warehouse approach → Janiek
- Gantt chart → Henrianne
- Critical path dependency & analysis → Neli
- Current situation analysis → Nienke
- Making sprint video → Max
- Making charts from old situation → Mike
- Work Breakdown Structure → Everyone
- Planning → has been made during our group meeting at 15/11/2021

Everything was discussed in our teammeeting at 15/11/2021.

# data[].attributes.body
12.00, Brightspace

# data[].attributes.body
- Every monday morning we have a teammeeting. Everyone is present, if not, this person should perform an additional task the upcoming week.
- During this teammeeting, we distribute the tasks for that week.
- Everyone completes his/her task before the next teammeeting, unless it needs to be submitted earlier (like the sprint video's).
- Every week another team member is responsible for the sprint video.

# data[].attributes.body
12.00, Brightspace

# data[].attributes.body
10.30, before the workgroup meeting

# data[].attributes.body
12.00, Brightspace

# data[].attributes.body
11.00, before our teammeeting

# data[].attributes.body
There is a lot of work to be done, so it needs to be well distributed over the available weeks. Since we are a group of 6 people, the arrangements for meetings must also be clear because a meeting is not easily rescheduled due to the different schedules of everyone. A good planning therefore shows how we are going to do things and how we can complete this project successfully and is therefore an important step in the project.

# data[].attributes.body
At the fourth seminar, one week has already passed for us as a group. This is a sort of first measuring point for how we are doing, whether everyone has kept to the agreements and it is a moment to get and discuss feedback. A good start is half the work, so if the first week has proved successful, it gives good hope and confidence for the following weeks. And in this way, every team meeting is actually a milestone.

# data[].attributes.body
12.00, Brightspace

# data[].attributes.headline
Project Milestone 3: Come up with a new lay-out

# data[].attributes.subject
Project Milestone 3: Come up with a new lay-out

# data[].attributes.body
Coming up with a new lay-out is, of course, the core of the project. Once we have a good idea for this, we can work it out completely, both visually and descriptively. So coming up with a new layout is crucial and an important milestone because the rest of the project actually depends on it.

# data[].attributes.body
12.00, Brightspace

# data[].attributes.body
- Make planning
- Warehouse approach
- Gantt chart
- Critical Path dependency
- Current Situation Analysis
- Make sprint video
- Make charts from old situation

# data[].attributes.body
11.00, before our teammeeting

# data[].attributes.body
- Discuss feedback sprint 1
- Discuss analysis from current situation
- New ideas about lay-out
- Maybe: new ideas about working process
- Make sprint video

# data[].attributes.body
- Discuss feedback sprint 2
- New ideas about working process
- Explain these new ideas
- Make lay-out + detailed description
- Make first part of chart to make visible the flow in the new situation
- Come up with Q&A questions
- Make sprint video

# data[].attributes.body
12.00, Brightspace

# data[].attributes.body
- Discuss feedback sprint 3
- Make charts
- Improvement of new design
- Costs & benefits analysis new situation
- Start preparing presentation
- Make sprint video

# data[].attributes.body
- Discuss feedback sprint 4
- Prepare presentation (text + slides)
- Write final reflection report
- Make sprint video

# data[].attributes.body
11.00, before our teammeeting

# data[].attributes.body
12.00, Brightspace

# data[].attributes.body
Light blue / aqua = in progress
Green = completed

# data[].attributes.body
Core task
Design a new lay-out

Sub-tasks
- Discuss analysis from current situation
- Discuss on what points CEVA can improve
- Come up with several ideas about a new lay-out
- Discuss what idea(s) is/are the best

# data[].attributes.headline
Tasks Sprint #5: Final Report & Presentation slides (20/12)

# data[].attributes.subject
Tasks Sprint #5: Final Report & Presentation slides (20/12)

# data[].attributes.body
08.00, Brightspace

# data[].attributes.body
10.30-12.15 final presentation

# data[].attributes.body
Strengths: diligent, stress-resistant, team player

Capabilities: good in planning, can adapt well
Area of desired growth: learning what it means to be a project manager, what is important to keep in mind and what to look out for.

Availability: available every day except for Tuesdays and Wednesdays due to work (every week).

# data[].attributes.headline
Project Milestone 4: Finish all the deliverables

# data[].attributes.subject
Project Milestone 4: Finish all the deliverables

# data[].attributes.body
By deliverables we mean the deliverables named in case 1. Once we have completed all of this, only the presentation remains. Finishing these deliverables (on time) will be a boost because the biggest part of the project is done. Hopefully we can then look back on the course of the project with satisfaction and focus on the final presentation and reflection report.

# data[].attributes.body
Strengths: persistent

Area of desired growth: experience how you can manage a project from begin to end.

Availability: every monday morning, tuesday morning.

# data[].attributes.body
Strenghts: Goal-oriented

Area of desired growth: Becoming familiar with setting up/executing a project so that I am already familiar with this in the future.

Availibility:
- Every Monday and Thursday
- On request flexible.

# data[].attributes.body
Strenghts: perseverance

Area of desired growth: I want to learn how to run a project in a good way.

Availability: I am available every Monday and Tuesday, but also on weekends.

# data[].attributes.body
Core task
Work out the new lay-out and come up with a new work process as part of that.

Sub-tasks
- Make lay-out visual
- Detailed description of new lay-out
- Come up with new ideas about working process
- Explain these new ideas
- Make chart to make visible the flow in new situation

# data[].attributes.body
Core task
Finish new situation & substantiate with cost-benefit analysis

Sub-tasks
- Improve our new design
- Finish charts
- Make costs & benefits analysis new situation
- Start preparing presentation

# data[].attributes.body
Core tasks
Make presentation & write final reflection report

Sub-tasks
Make presentation:
- Write presentation text
- Make Powerpoint slides
- Prepare/practice the presentation

Write final reflection report:
- Discuss the planning phase (using the questions stated in the assignment)
- Reflect on how the team worked together (using the questions stated in the assignment)
- Think about what we learned
- Spelling and grammar check
- Lay-out

# data[].attributes.body
Strengths: goal-oriented, perseverance

Area of desired growth: I want to get a better idea of what a project manager is doing, what skills it involves and to develop these skills myself. I also think it is a challenge to strive for one goal with a group of six people and to manage this well.

Availability:
- Every monday morning
- Every tuesday
- Every wednesday morning
- Not available in the evenings

# data[].attributes.body
Strengths: accurate, organized

Area of desired growth: experience the skills of a project manager and develop myself to become a good project manager.

Availability: every Monday and Wednesday morning, and flexible on request

# data[].attributes.headline
Project Milestone 5: Handing in the presentation slides and reflection report

# data[].attributes.subject
Project Milestone 5: Handing in the presentation slides and reflection report

# data[].attributes.body
Once this is turned in, the project is pretty much done. In the morning we only have to actually present and then the project is really over. That will probably be a big relief after weeks of working towards this day.

# data[].attributes.body
We have decided to record the sprint videos at the end of the team meetings because that is the only time we can all be together. We think we made a good division of tasks over the weeks and certainly with the six of us we think we should really be able to do it. We do expect that coming up with a new design in the second week could be a big challenge. Since the rest of the project has to build on that, it needs to be done right.