What I think Scrum is?
Scrum provides a basic framework for organization of a Product Backlog - which includes functionalities, features, technologies, enhancements and bug fixes for a software development team.
Scrum Team is self-organizing, and is most effective when its team members are reliable, and take initiative to discuss what goes into the Product Backlog at the First Sprint Meeting Overview. Thereafter, the team conducts several sprints (iterations), to achieve and design the final product.
Daily Scrum Meetings are held to facilitate discussions among team members, and get everyone updated on what everyone else is doing or have done. This lasts just 15 mins. Only the pigs (i.e. people who are core team members, committed to the project) can talk. People who are just there as extra help (i.e. chickens, who are just involved), should not be allowed to interfere with Scrum Meetings. This reduces potential distractions, and helps the Scrum Team focus on its main purpose and objective. It also helps the team iron out problems, and help out team members who may be facing problems with Sprint assignments. Teamwork is the key here.
A Scrum Review Meeting is held after every Sprint, to assess the effectiveness of the Sprint, and how best to plan for the next sprint.
Why I think Scrum Works - Even for Small Teams
Scrum is useful in that it enables a team to understand its integral strengths and weaknesses. It provides a platform for team members to help out one another in weaker areas, and enable stronger team members to focus on what they do best. Teams are self-organizing and help out in everywhere they can - as a result, work gets done much faster and productivity increases.
Scrum gives people a chance to cut through the noise. Basically, it gives team members to chance to focus on what is important, and eliminate what may seem cool - but is actually unimportant to the progress of the team.
Scrum gives team members a chance to talk at every Scrum Meeting, highlight impediments to be overcome, and provide updates. From my numerous experiences working with different people, I realize that communication is of utmost importance. Sometimes, people can just clam up and refuse to highlight problems and choose to stay silent. Scrum certainly provides an open and receptive environment to overcome this issue.
How I think Scrum can be used in CS3216
The usual sprint lasts 30 days. This is unfeasible in 3216 due to the much shorter time duration given between assignments. I think it is better to start with 3 day sprints? This will enable team members who have never used Scrum before to adapt to Scrum gradually, and keep changing and adapting to requirements, update Product Backlog, come up with better Sprint Goals and Sprint Backlog - basically adapting to the situation as the situation calls for change.
Use of Google Docs to post all Scrum Backlogs, Project Timelines, Agenda - team members can just update Google Docs and work anywhere and anytime.
The best Scrum Teams work in familiar environments. Ken Schwaber advocates Daily Scrum Meetings to be held at same place, same time. This may not be feasible due to different timetables lack of designated Scrum Rooms. Still, this is a problem that can be easily overcome.
Scrum is fluid in nature. Don't let anything be cast in stone and be prepared for change as it comes.
P.S. am really new to this. Let me know of suggestions and how we can implement Scrum better. I will post again after we have tried it in practice.
