Posts Tagged ‘ Traditional Project Management ’

An Introduction to SCRUM Framework

June 12, 2017
By
An Introduction to SCRUM Framework

A Scrum project involves a collaborative effort to create a new product, service, or other result as defined in the Project Vision Statement. Projects are impacted by constraints of time, cost, scope, quality, resources, organizational capabilities, and other limitations that make them difficult to plan, execute, manage, and ultimately succeed. However, successful implementation of the results…

Read more »

User Story Prioritization Techniques

June 7, 2017
By
User Story Prioritization Techniques

At the program or portfolio level, there is normally a smaller number of requirements/user stories than at the project level. The percentage of user stories with a very tangible value/business need/user impact is normally much lower than on project level. That means that the selection of techniques that are useful at a program or portfolio…

Read more »

Conflict Management and SCRUM

June 1, 2017
By
Conflict Management and SCRUM

Organizations applying the Scrum framework encourage an open environment and dialogue among employees. Conflicts among Scrum Team members are generally resolved independently, with little or no involvement from management or others outside the Scrum Team.  Conflict can be healthy when it promotes team discussions and encourages debates, as this usually results in benefits for the…

Read more »

Agile vs Waterfall?

May 24, 2017
By
Agile vs Waterfall?

Agile and Waterfall are two different methods used in managing a project. Both the methods have their own pros and cons and choosing one model is based on many project-centric factors. Waterfall Method The Waterfall model is a progressive design process which in the software development industry goes through stages such as Conception, Initiation, Analysis,…

Read more »

Agile User Stories

May 18, 2017
By
Agile User Stories

User Stories adhere to a specific, predefined structure and are a simplistic way of documenting the requirements and desired end-user functionality. A User Story tells you three things about the requirement: Who, What, and Why. The requirements expressed in User Stories are short, simple, and easy-to-understand statements. The predefined, standard format results in enhanced communication…

Read more »

All About Prioritized Program Backlog

May 12, 2017
By
All About Prioritized Program Backlog

The Prioritized Program Backlog plays a very similar role at the program level as the Prioritized Product Backlog does on project level. It identifies the requirements for the program and their priorities. The items in the Prioritized Portfolio Backlog provide inputs to the various Prioritized Program Backlogs and, through Prioritized Program Backlogs, to Prioritized Product…

Read more »

How to Choose Scrum Master(s) and Stakeholder(s)?

May 12, 2017
By
How to Choose Scrum Master(s) and Stakeholder(s)?

Selecting appropriate Scrum Master(s) and identifying relevant Stakeholder(s) is crucial to the success of any project. In some projects, there may have been pre-conditions stipulating certain team members and their roles. When there is flexibility in choosing the Scrum Master(s), the following are important Selection Criteria: Problem-solving skills—This is one of the primary criteria to…

Read more »

How Program Product Backlog Works?

May 12, 2017
By
How Program Product Backlog Works?

The Program Product Owner develops the Program Product Backlog which contains a prioritized list of high level business and project requirements preferably written in the form of large Program Backlog Items. These are later refined by the Product Owners of individual projects as they create and prioritize Product Backlogs for their projects. These Prioritized Product…

Read more »

What is Servant Leadership?

May 3, 2017
By

The preferred leadership style for Scrum projects is Servant Leadership. This term was first described by Robert K. Greenleaf in an essay entitled The Servant as Leader. Below is an excerpt where he explains the concept: The servant-leader is servant first…It begins with the natural feeling that one wants to serve, to serve first. Then conscious…

Read more »

Various Dimensions of Team Specialization

April 25, 2017
By
Various Dimensions of Team Specialization

In a large SCRUM project, Team Specialization may be required. There are three dimensions of Team Specialization. The first dimension is the need for accomplishing specific tasks. For example, one Specialized Team might be an integration team that has specialized knowledge of continuous integration.. That knowledge could be especially important when and if there is…

Read more »

Subscribe

Follow Us On