Skip to main content

Posts

Showing posts with the label Skills Of Scrum Master

Tracking and Communicating Progress in Agile

Information radiators are meant to display information at a public place so that the information can be noticed by as many people as possible without making a conscious effort to do so. The idea of information radiator was invented by Alister Cockburn, who was a big believer in effective and timely communication. Information Radiators should display the current information about the project whatever is critical for the team to learn. It could include Schedule, tasks, issues, progress etc. The Most common forms of Information Radiators are ·         TaskBoards or Kanban Boards ·         Big Visible Charts such as BurnDown Charts ·         Street Lights and Lava Lamps Characteristics of Information Radiators which make the Information Radiators work ·         Simplicity : The information Radi...

What is Definition of Done?

Done Criteria are a set of rules that are applicable to all User Stories. A clear definition of done is critical because it removes ambiguity from requirements and helps the team adhere to mandatory quality norms. This clear definition is used to create the Done Criteria when a Prioritized Product Backlog is prepared. Definition of done is crucial to a highly functioning Scrum team. The following are characteristics that you should look for in your team’s definition of done. Verifying that your team’s DoD meets these criteria will ensure that you are delivering features that are truly done, not only in terms of functionality but in terms of quality as well. DoD is a checklist of valuable activities required to produce software. Definition of done is a simple list of activities (writing code, coding comments, unit testing, integration testing, release notes, design documents, etc.) that add verifiable/demonstrable value to the product. Focusing on value-added step...

Distributed Scrum Teams

Today businesses are shifting to emerging economies (such as India) due to reduced business operations cost and an easily available workforce. The businesses certainly are more virtual and distributed, with "distributed" as its key element. Thus the need for better managing such teams, using the right tools and processes, is becoming increasingly critical for any enterprise company. Here are some reasons for the shift and need for having distributed Agile teams: ·           Globally distributed teams reduce costs. ·           They can reach the market more quickly with a "follow the sun" model. ·           Distributed teams expand access to new markets. ·           Acquisitions as a result of consolidation results in companies working together to integrate their businesses. ·   ...

What are the skills needed for Product Owner and Scrum Master?

Skills of a Product Owner Choosing the right product owner is crucial for any Scrum Project. Following are some of the characteristics expected from the Product Owner ·           Visionary : Product owner should be able to envision the final product. ·           Doer : Product owner should also be a doer – that means, he should work with the team to get the final product ready. ·           Product Owner should be a Leader and Team Player ·           Communicator : The product owner must be an effective communicator and negotiator. The Product Owner is the Voice of the customer and therefore he should communicate customer needs and requirements and bridge the gap between the customer and the team. This may mean saying NO sometimes to the customer. ·        ...