Team meeting and SCRUM strategy

Mondays
Email from Lead Project Manager to All Staff with bullets outlining the coming week’s work to be accomplished by each resource. This benefits each employee to know what is expected of them, and lets the product and management team have a viewable checklist of what they can expect to have accomplished. It also emphases the important of not derailing the resources with off the radar tasks, and asks if they can be prioritized for the following sprint (2 weeks) instead.

No *SCRUM are required on Mondays, but the team is encouraged to speak to their peers for needs they in shared projects.

End of day project report required. Time is logged toward sprint bugs. Note for Tuesday stand-up meeting to speak about whether the programming tasks were successful, and if not, what was in your way and how that impacts the sprint.

Tuesday – Friday
15m SCRUM details whether or not you logged 5 hours of programming time toward your milestone and if the time estimate it took to complete was approximately correct.

End of day project report required. Time is logged toward sprint bugs. Note for Tuesday stand-up meeting to speak about whether the programming tasks were successful, and if not, what was in your way and how that impacts the sprint.

Friday
In addition to SCRUM meetings, each team attends a 1 hour general meeting @ 3pm to recap the week and talk about ideas. The teams, in our case Back-End team, Front-End, & Product Team (includes project & product management + QA, covers assessment of the resource calendar and alignment of info on the wall board). We will alternate meeting spaces weekly as to each have an opportunity to use The Lounge™, boardroom and lobby spaces. Following, at 3pm all teams meet together in The Lounge™ for a similar style meeting with each team having a representative to explain what their team achieved and bring to the table ideas, or the progress on ideas. Beer during and foosball after.

 

admin