User:Randyfisher/CSL/Check In

CSL Campaign 2011

(CSL Campaign 2011 - is the CSL version of tax season - an intense period of activity, to service and proactively engage with our stakeholders)

• We have a 20-day campaign, bounded by the November 20 course registration deadline.
• We benefit from prior experience and planning in meeting the goals of the Campaign
• We can quickly respond to changing needs and requirements - when we are all informed, and coordinated in our activities.
• We recognize that we don't have the time to understand all of the problems, but we can act in a coordinated and informed manner - to meet our goals.

Check In

• Is a means for our team members to be aware of what others are doing
• Identify what challenges we are dealing with
• Help each other meet the desired daily goals and Campaign goals

• The main roles in Scrum are: CSL Manager, Placement Officers, and Work Students (if available)

Daily Check-In

Each day during the CSL Campaign, a daily check-in (project status) meeting occurs - with specific guidelines:

• The meeting starts precisely on time.
• All are welcome, but normally only the core roles speak (i.e., CSL Manager, Placement Officers, Work Students (if available)
• The meeting is time-boxed to 15 minutes
• The meeting should happen at the same location and same time every day

During the meeting, each team member answers four questions:

1. What have you done since yesterday?
2. What are you planning to do today?
3. Do you have any problems that would prevent you from accomplishing your goal (i.e., what you are planning to do today)?
4. What help do you need?

Notes

• It is the role of the CSL Manager to facilitate resolution of any barriers, although the resolution occurs outside the Daily Check-In itself to keep it under 15 minutes.)
• Key process steps will be identified, and added to Key Timelines and Dates; Orientation Manual; and Winter 2012 Project Tracking Summary

---

Original Notes

Scrum is an iterative, incremental framework for project management often seen in agile software development, a type of software engineering.

Although the Scrum approach was originally suggested for managing product development projects, its use has focused on the management of software development projects, and it can be used to run software maintenance teams or as a general project/program management approach.

Scrum is a process skeleton that contains sets of practices and predefined roles. The main roles in Scrum are[7]:

1. the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager)
2. the “Product Owner”, who represents the stakeholders and the business
3. the “Team”, a cross-functional group who do the actual analysis, design, implementation, testing, etc.

Sprint / Campaign

A sprint / Campaign is the basic unit of development in Scrum. Sprints tend to last between one week and one month,[6] and are a "timeboxed" (i.e. restricted to a specific duration) effort of a constant length.

Each sprint is preceded by a planning meeting, where the tasks for the sprint are identified and an estimated commitment for the sprint goal is made, and followed by a review or retrospective meeting,] where the progress is reviewed and lessons for the next sprint are identified.

During each sprint, the team creates a potentially deliverable product increment (for example, working and tested software). The set of features that go into a sprint come from the product “backlog”, which is a prioritized set of high level requirements of work to be done. Which backlog items go into the sprint is determined during the sprint planning meeting.

Scrum enables the creation of self-organizing teams by encouraging co-location of all team members, and verbal communication between all team members and disciplines in the project.

A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called requirements churn), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team’s ability to deliver quickly and respond to emerging requirements.

Daily Check-In / Scrum

Each day during the Campaign, a project status meeting occurs. This is called a daily check-in. This meeting has specific guidelines:

• The meeting starts precisely on time.
• All are welcome, but normally only the core roles speak (i.e., team members, project manager)
• The meeting is time-boxed to 15 minutes
• The meeting should happen at the same location and same time every day

During the meeting, each team member answers three questions:

• What have you done since yesterday?
• What are you planning to do today?
• Do you have any problems that would prevent you from accomplishing your goal (i.e., what you are planning to do today)?

(: It is the role of the ScrumMaster to facilitate resolution of these impediments, although the resolution should occur outside the Daily Scrum itself to keep it under 15 minutes.)