There are positive and
negative stakeholders in every project (according to PMBOK). Positive ones will
benefit from project implementation, for example their work will become more
effective, more automated, easier, and more fun. At the same time negative
stakeholders will have problems once the project is implemented. For example,
they will be fired because their job will be done by new software.
Search This Blog
Friday, 19 October 2012
Thursday, 20 September 2012
Type of Project Reports
Most of the organizations
have their own template for reports, in addition to that the Project Manager
and your team has their own format.
Each report takes own time to
collect information, write, read, maintain and act on the action items.
Based on my experience, come
up with the important reports required in the project, purpose and the
important aspects needs to be covered in the report.
Thursday, 16 August 2012
Importance of Non Functional Requirements
The functional requirements
are day-to-day requirements which business users and stakeholders needs in the
product.
It is important to consider
the other requirements also; these are called “Non-Functional Requirements” and
fits into the organization's operational environment. This is the obvious
requirements that your business users may not think about it.
Wednesday, 13 June 2012
Velocity in Agile Projects
This article talks about calculating the
team velocity of the agile project and addressing the benefit of the team
velocity.
Velocity is an extremely simple, powerful method for
accurately measuring the rate at which teams consistently deliver business
value.
It
is a measure of how much product backlog items the team can complete in the given
amount of time.
Monday, 28 May 2012
Kanban Board for Agile Projects
In agile projects it’s common practice to visualize and project status in white board of the project war room.
The lean management in the production industry also uses this kind of practice.
“Kanban” in Japanese means, loosely translated card or sign. The kanban boards used to view the three point’s time task and team so that the whole team understands the current status of the project and work n an autonomous, motivated and collaborative manner.
Subscribe to:
Posts (Atom)



