Friday, February 20, 2015

Scrum Activities Overview

Sprint Planning Meeting

First Half

Duration: 2 hours (for a 2 weeks spring), but should be scaled to the length of the sprint. For example, 4 hours for a 4 week sprint.
Frequency: Before starting a sprint
Participants:
  • Scrum Master
  • Development Team
  • Product Owner
  • Steakholders

Deliverables:

  • Product Backlog (user stories) that is prioritized and estimated in terms of hours or difficulty.
Description: Agree on what should be in the sprint

Second Half

Duration: 2 hours (for a 2 weeks spring), but should be scaled to the length of the sprint. For example, 4 hours for a 4 week sprint.
Frequency: Before starting a sprint
Participants:

  • Scrum Master
  • Development Team
  • Product Owner
  • Steakholders

Deliverables:
  • Sprint Backlog that contains development tasks that will fit that the development team thinks can be completed during the sprint
  • Plot ideal burn-down chart
Description: Hashout plan for sprint

Daily Scrum Meeting (aka Stand-up meeting)

Duration: 15 minutes
Frequency: Daily
Participants:


  • Scrum Master
  • Development Team
  • Product Owner
  • Steakholders
Deliverables
  • Impediments (recorded by Scrum Master).
    NOTE: Not resolved during this meeting.
Description:
The scrum master asks each person on the team three questions:
  • What did you accomplish yesterday?
  • What are you working on today?
  • What impediments are in your way?

Daily Updates

Update Sprint Burndown Chart: At the end of each day each developer updates the number of hours remaining for the task s/he is working on.


Sprint Review Meeting

Duration: Max of four hours
Frequency: At the end of the sprint
Participants:
  • Scrum Master
  • Development Team
  • Product Owner
  • Steakholders
Deliverables
  • Feedback from product owner, steakholders
Description:
Demonstration of what was implemented in the spring


Sprint Retrospective Meeting

Duration: Max of 3 hours
Frequency: At the end of the sprint
Participants:
  • Scrum Master
  • Development Team
  • Product Owner
  • Steakholders
Deliverables
  • Document:
    • What went well during the sprint?
    • What could be improved in the next sprint
  • Improve process as needed
Description:
Reflect on the sprint.


References:

Monday, February 2, 2015

Grant Permissions to create, alter, or view definition of a view in SQL Server


Let's assume you have a SQL Server user called reporting_user and it has select only access to some tables. To give that user the ability to create views use the following statements (be sure to change reporting_user to the name of your user).

grant create view to reporting_user
grant select on schema :: dbo to reporting_user
grant view definition on schema :: dbo to reporting_user