Previous Lecture Lecture 16 Next Lecture

Lecture 16, Tue 11/01

Tue Lecture: First Retrospecive (Retro)


Reminder: Speed Advising Tomorrow

See announcement from last Thursday’s lecture

Speed Advising: Wed Nov 2, 2pm-6pm, HFH 1132, Refreshments Served.

speed advising flyer

Today (outline)


You may merge PRs and submit even if you don’t (yet) have 100% code coverage or mutation coverage, but there may be deductions for that, so continue working on that if you can make the time to do so. (If it’s fixed before we get around to grading it, there is no penalty, though that would be an extra PR.)

Retrospective: the heart of Agile

The core principle of Agile is “inspect and adapt”.

Inspect and Adapt is, in many ways, linked to the Scientific Method;

All in the service of doing a better job of software development.

In a retro, the team stops, pauses, reflects, and most importantly comes up with an actionable change for their practice.

Today’s Retro


Check that each member of the team is able to access the folder.

In that folder, create a folder called Retros and in that folder, create a document Retro1

Then follow the instructions in the article for Stop/Start/Continue retro.

In the document, write down who your retro leader is.

At the end of the process, you should have in your document:

After the retro is done, you can: