Iterations¶

Summary of project work in interations.

S01 ( 06.03.2023 - 19.03.2023 )¶

• selection of a suitable IDE - Visual Studio
• specification of requirements
• agreement that everyone has to learn c++ (nobody knows c++)
• introduction to cMake
• gitflow settings
• setting meeting times (Saturday 9:00 (planning + retrospective) + Wednesday 17:00)

S02 ( 20.03.2023 - 26.03.2023 )¶

• getting the program up and running
• source code analysis
• workshop with the client about cMake and project requirements
• creation of a project plan
• configuration of Redmine and setting conventions

Retrospective¶

GLAD:

• TK - Vasek made a nice plan
• TK - Compared to the previous sprint we are more coordinated, more efficient
• MJ - Better planning
• JK - Clarifying the procedure with the mentor

SAD:

• TK - I don't really understand the code
• JK - The code is complicated

MAD:

• VŠ - we are a little behind schedule
• VŠ - we need to correctly specify the requirements for each task (optimizing is not a sufficient description)

S03 ( 27.03.2023 - 02.04.2023 )¶

• workshop with the client about mathematical background of the project and source code structure
• risk analysis document prepared
• vision document prepared
• source code analysis of ARAP and PBD

Retrospective¶

GLAD:

• JK - the meeting with the author of the project was very useful
• TK - the meeting with the author helped me to get a better understanding of the code
• VŠ - the meeting with the author was good
• VŠ - we made up for the initial delay in the plan
• TK - Vasek played nicely with the administration

SAD:

• TK - I analyzed a lot of things, but I still don't feel like I have a proper understanding of how everything works
• JK - lots of work, little time
• VŠ - Mathematically challenging project, big overhead for analysis
• VŠ - We will descope cMake refactoring to the next sprint

MAD:

• VŠ - We still have a big slippage, we should escalate the situation better
• VŠ - Tomas writes Czech in Redmine
• VŠ - We need to improve communication in the team, we don't have a very good overview of the status of the individual tasks

S04 ( 03.04.2023 - 09.04.2023 )¶

• consultations with client about PBD and ARAP merge
• architecture document first part prepared
• internal convention document prepared
• resolving super-build issue

Retrospective¶

GLAD:

• JK - better understanding of the mathematical part of the method

SAD:

• JK - a team member couldn't handle the time pressure
• JK - high mental load

MAD:

• TK - MJ left us
• VŠ - basically zero progress on Cmake, I started implementing from scratch
• VŠ - missing team member + delay on cMake will make big problems for on-time delivery

S05 ( 10.04.2023 - 16.04.2023 )¶

• Setting new targets - removing a task for comparison of results
• Testing is unlikely to be as high quality due to time constraints

Retrospective¶

GLAD:

• TK - The client is helpful and supportive
• VŠ - We have the first implementation deliverable
• VŠ - Improved team communication
• VŠ - Moving the meeting to Sunday evening is better for closing tickets
• TK - I better understand the connection of building c++ projects (Cmake etc.)
• JK - positive feedbakc from ASWI mentor
• TK - Vasek made nice documents => lots of points on ASWI evaluation
• VŠ - team morale is not dropping (probably could now be less now)

SAD:

• JK - Mental state remains unchanged
• VĚ - Every step of putting together a project results in a problem that blocks development

MAD:

• TK - I'm already on my second week of almost 0% progress and it's severely demoralizing (despite X hours spent on the task)

Actionable points¶

• Trying to get the project to a state where we can start implementing as soon as possible
• Help from the author + focus on the build process
• Lunch together to boost team morale
• Incorporate deadlines from other coursework into deadline planning

S06 ( 17.04.2023 - 23.04.2023 )¶

• oSim superbuild is working now on Win
• Fixing an unexpected bug that was in our project
• ARAP method - the project is in a state where we can address the combination of both methods
• We have received from the project author his proposal for a solution to the combination of methods

Retrospective¶

GLAD:

• JK - quite a lot of implementation progress
• JK - having lunch with the team was beneficial, I got motivated to continue my studies
• TK - finally something is working -> big boost to morale
• TK - Client satisfied with our bug fix
• VŠ - One big feature was descoped, according to our new plan, we should be able to delivery everything on time

SAD:

• JK - time pres from other subjects
• TK - I'm scared that we won't be able to get everything done in time
• VŠ - In superbuild there is often a problem with external libraries (can't be translated, not compatible, other problems) - this creates blockers that prevent further progress and are time-consuming to resolve (hard to estimate time to resolve these kind of problems)

MAD:

• TK - I managed to forget about half of the mathematical background

Previous actionable points outcomes¶

• Project is now in runnable state - perfect
• Lunch together to boost team morale was good

Actionable points¶

• Create a prototype of the combination of PBD & ARAP methods
• Implement at least one of the two possible combinations (using scales or using a combination of kinetic forces)
• Would be helpufull to have one GIT repo for both features, current situation might lead in merge issues

S07 ( 24.04.2023 - 30.04.2023 )¶

Retrospective¶

GLAD:

• JK - A promising proposal for a solution
• JK - I'm more familiar with the algorithm and code than in previous sprints
• VŠ - CI/CD integration went relatively smoothly

SAD:

• TK - The time pres is still growing
• VŠ - Superbuild unfortunately doesn't work on Linux yet

MAD:

• TK - Vasek is deleting my retrospective points, he's a dictator

Previous actionable points outcomes¶

• It was not possible to implement one of the two options, but we have a promising proposal for a solution

Actionable points¶

• Prototype a combination of PBD & ARAP methods
• Adhere to the meeting date (Sunday 20:00)!!!
• Overestimating workload when we know we'll be working more

S08 ( 01.05.2023 - 07.05.2023 )¶

Retrospective¶

GLAD:

• JK - Merge of methods is now maintaining volume
• TK - I feel that we could move the project to a satisfactory form for the client.
• VŠ - Tomas prepared a retrospective during my absence
• VŠ - Team morale is increasing and results are becoming visible

SAD:

• TK - Honza was late to the retrospective
• VŠ - Honza is late for meetings
• JK - There was no lunch together to boost morale
• TK - I understand the limitations of ARAP, but implementation by client is a bit different
• JK - deadlines for midterms

MAD:

• JK - ASWI administration is basically useless to me and keeps me from my work

Previous actionable points outcomes¶

• Meeting are still being postponed !!!
• During the current planning it was discussed that we will have more time (Tomas) and less time (Vasek) for implementation and this was taken into account

Actionable points¶

• Break down the comments in the tasks more for a better overview (aimed at Honza)
• Make timesheets on time so I can close the sprint on time
• Adhere to meeting schedules

S09 ( 08.05.2023 - 14.05.2023 )¶

Retrospective¶

GLAD:

• JK - new insights from the code author
• TK - according to the code author, it is not necessary to apply Laplacian constraints or cotan weighting, which is not trivial
• JK - at least superbuild is on track
• TK - we have a notion of the process and order in which each method must be applied to deliver acceptable results
• VŠ - we are starting to come to the end
• VŠ - timesheets on time
• VŠ - meetings on time, perfect

SAD:

• JK - The time and mental burden of other subjects is becoming unbearable
• TK - I agree with JK -^
• VŠ - Fixing errors in external libraries was not taken into account in the planning - we will draw on the time pool "reserve"

MAD:

• TK - We've tried a lot, but it doesn't look like it based on the added lines of code (trial & error)

Previous actionable points outcomes¶

• Timesheets & meetings on time - perfect

Actionable points¶

• Arrange a meeting with the client and present the current status

S10 ( 15.05.2023 - 21.05.2023 )¶

Retrospective¶

GLAD:

• JK - quite important new information from a client
• VŠ - everything is going pretty well
• TK - I managed to implement Laplacian smoothing
• TK - I got an A on my first exam

SAD:

• JK - information from the client came quite late (partly our fault)
• TK - due to new information we had to postpone testing
• TK - less time for the project (exam time starts)

MAD:

• TK - important info from the client very late!

Previous actionable points outcomes¶

• the client has reviewed the current status of the implementation
• the postprocessing method was applied with minimal result

Actionable points¶

• start with testing

S11 ( 22.05.2023 - 28.05.2023 )¶

Retrospective¶

GLAD:

• JK - Now there could be more time for TSP - project completion
• TK - we are finally getting to the finish

SAD:

• JK - problems with superbuild
• TK - I can't work on the project because of exams
• TK - team morale is declining (we are all behind schedule and have a lot on our plate)
• VŠ - despite including a time margin in the estimations, the last iteration didn't go well

MAD:

• JK - the last 3 weeks have been extremely exhausting and time consuming
• TK - I'm not keeping up with anything properly, this semester has been packed

Previous actionable points outcomes¶

• testing started

Actionable points¶

• finish the project

S12 ( 29.05.2023 - 04.06.2023 )¶

Retrospective¶

GLAD:

• JK - last meeting (project)
• VŠ - project brought to a final state
• TK - it's finally over
• JK - the project has been knowledgeable for us
• TK - new insight into working on a team project

SAD:

• JK - last meeting with teammates
• TK - no more team lunches to boost morale
• VŠ - failed to finish everything as originally planned

MAD:

• TK - the result at first sight may not correspond to the hours spent
• TK - very time-consuming due to the missing member

Previous actionable points outcomes¶

• project hopefully managed to the end