Today's instructor was Stein Dolan, from Microsofot.
We learned that Agile is all about Values & Principles. There are defined tools and processes to implement Agile.
Agile Manifesto
We value -
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Should every sprint duration be equal?
Yes - it helps a lot. We can get better data over time which can help determine team's velocity for a given time duration.
Also, team resource changes also should happen at beginning of new sprints only to assure team and sprint efficiency.
We were asked about our goal to join the class.
I have done scrum in the past. I did that with self-learning to begin with, and I liked the visibility Burn-down charts represented.
Then I worked on a project at Microsoft, where we implemented Scrum with the tool - Tackle. That team was rocking. Team members have already estimated the work item in hours. Every day, team would enter hours they worked on any work item, and if they want to re-estimate. So, at the end of the day, we can easily see if everything is on track. I have seen this work, and so much appreciate the visibility. For me - this kind of visibility is primary reason to do scrum. But, I want to know more details on how to build these processes.
We learned about the roles in the Scrum.
Product Owner (PO) - is the person(s) who is responsible for all inputs(requirements) and outputs(releases).
Scrum Master - is the person who facilitates sprint and stand up meetings. He is supposed to make blocking issues and team collaboration smoother.
Team - is responsible to work estimates and implementation.
Product owner focuses on Vision, Product and Releases.
Team focuses on Day, Sprint and Releases.
We are going to perform some exercise on a given project definition. It will fun.
0 comments:
Post a Comment