{"id":727,"date":"2018-12-02T22:09:38","date_gmt":"2018-12-03T03:09:38","guid":{"rendered":"http:\/\/www.modelb.biz\/?p=727"},"modified":"2018-12-02T22:09:38","modified_gmt":"2018-12-03T03:09:38","slug":"py19-iteration-1-review-and-retrospective","status":"publish","type":"post","link":"https:\/\/www.modelb.biz\/py19-iteration-1-review-and-retrospective\/","title":{"rendered":"PY19 Iteration 1 Review and Retrospective"},"content":{"rendered":"
The first third of our 2019 planning year is coming to a close and it is time for our first Review\/Retrospective covering the last two months of work.\u00a0 After this, we will go dark for December to enjoy the holidays and rest up before the second third of our planning year (January – April).<\/p>\n
With our work transitioning from development to testing and marketing, we have shifted from Scrum based sprints<\/a> to Kanban<\/a> based iterations.\u00a0 This post will cover the results and lessons from two Kanbans, 1.1 and 1.2.\u00a0 As always, you can get all the details by from our weekly stand ups<\/a>.<\/p>\n Agile reviews are an opportunity to hold ourselves accountable by identifying how much of what we planned we actually completed.<\/p>\n Agile retrospectives are the means by which we “inspect and adapt”.\u00a0 This is our chance to promote what works and adjust what does not.<\/p>\n The first third of our 2019 planning year is coming to a close and it is time for our first Review\/Retrospective covering the last two months of work.\u00a0 After this, we will go dark for December to enjoy…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12],"tags":[41,89,57,98],"acf":[],"yoast_head":"\nReview<\/h1>\n
Claiming Done<\/h2>\n
\n
Not Claiming done<\/h2>\n
\n
Retrospective<\/h1>\n
What went well?<\/h2>\n
\n
What did not go well?<\/h2>\n
\n
What can we do better?<\/h2>\n
\n