Thursday, 18 September 2014

Is Scrum Master a full time role?

It is not uncommon in a Scrum Master training classes to encounter questions such as “Is being a Scrum Master a full time role?”, or “How much time does a Scum Master contribute towards his role?”, or “Can a person from the development team multitask as a Scrum Master?”
New Scrum Masters might be apprehensive about the role that they might play as future Scrum Masters. However, certified Scrum Masters need to truly understand the responsibilities of a Scrum Master to realize the vital role played by them. The success of a Scrum project rests equally on the shoulders of the Product Owner, the Scrum Master, and the Development team. While the Product Owner and the Development team have their clearly established roles and responsibilities, it might seem that a Scrum Master performs only support roles such as coordinating meetings, removing impediments that are plaguing the team, or shielding the team from interference from the Product Owner.  This might make the Scrum Master seem like a glorified nanny.
Even organizations too sometimes view the Scrum Master role as a part time role. There can be several reasons why Scrum Masters are part time roles. The organization might be short of human resources to have a dedicated Scrum Master or the organization does not consider the Scrum Master’s role worthy of a full time role.
There is an obvious conflict if a developer also performs the role of a Scrum Master. This takes away the objectivity that is required in a Scrum Master while dealing with issues related to the Product Owner or even internal conflicts.
So, let’s focus on the issue where the role of Scrum Master is not considered substantial enough to be a full time role. Sprints in Scrum, unlike stages in waterfall, are intensive periods of activity where development takes place. Any impediments that are not resolved immediately can have an effect on the success or failure of a sprint. The Scrum Master not only resolves impediments as and when they arrive, but also has keen foresight to spot potential issues and create an environment that can help avoid any issues to occur.
The Scrum Master undoubtedly assumes the role of a leader. He coaches and mentors team members both at an individual and a group level to get the best out of the team. He also ensures the team collaborates smoothly and the team delivers what they committed to.
It might seem that a Scrum Master’s responsibilities are vague and general. However, most of the Scrum Master’s responsibilities are performed behind the scenes that require a strong understanding of multiple dimensions such as people, domain, and business requirements.

To know more click on:  http://www.scrumstudy.com/blog/

Thursday, 4 September 2014

What is AGILE?

Agile methodology is a dynamic project management approach to software development and implementation. Within a few years of its inception, Agile methodology has become popular because it is both developer and customer friendly. This is because—unlike the traditional Waterfall approach—Agile methodology is an adaptive approach that permits changes and modifications to be incorporated into the overall project plan at multiple points.
The hallmark of Agile methodology is the incremental and iterative approach to software development. In other words, the entire project is broken down into various customer-valued features that are developed in small repetitive cycles so that these features are delivery ready at the end of each iteration. The frequent delivery of business-valued features is customer as well as developer friendly. This is because, first, the technical team and stakeholders work collaboratively; second, this saves time and money; third, constant feedback from stakeholders enables developers to continuously evolve the software; and last, this promotes lightweight framework with more emphasis on working software than on documentation.
One of the key practices is daily meetings in which the team members inform the entire team on the progress of the project and discuss issues faced and obstacles. This helps the team foresee potential risks and work toward resolving them. Thus, close communication among the team members, increased productivity, evolutionary approach and reduced risks are the four pillars of the Agile methodology. Agile can be best described in the following four basic principles enshrined in the Agile Manifesto:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan