How you get best out from your team

1. Using tool and techniques
                  1. Reviews
                   2. Peer programming
                   3. RACI
                   

If a person poor in communication

If a person poor in communication better to check his work personally for the verification. 

•There is more to being a really good project manager than knowing PM processes, being a good leader, and having lots of experience. Try these seven traits on for size:

          –Enthusiasm for the project–Ability to manage change effectively–Tolerant attitude toward ambiguity–Teambuilding and negotiation skills–Customer-first orientation–Adherence to business priorities–Knowledge of the industry and technology

good company description

About the Powershop delivery team, compressed: Scrum. Two week sprints. Small multidisciplinary teams, integrated design and test. Business stories solved by delivery teams. Positive, mandatory code reviews. Beautiful code. Test all the things! Two days/month to work on your own projects. Family friendly. No crazy hours. No unrealistic deadlines. No unnecessary meetings. Everyone on one floor together. Speak your mind and your peers listen. Consistent culture from CEO down.

Project Constraints

Resource Leveling and Resource Smoothing

Resource Leveling and Resource Smoothing are Resource optimization Techniques

Resource leveling

“A technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply.” – PMBOK® Guide Fifth Edition.

Resource Smoothing

“A technique that adjusts the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits.”– PMBOK® Guide Fifth Edition.

(http://www.izenbridge.com/blog/underlining-the-differences-between-resource-leveling-and-resource-smoothing/)

Waterfall model Project Management Vs Agile Project Management

Project Manager moving to Agile Project Management from waterfall model see the difference,

-Individuals and interactions over processes and tools

-Working software over comprehensive documentation

-Customer collaboration over contract negotiation

-Responding to change over following a plan

twelve agile principles

1. Early and Continuous Delivery
2.  Welcome changers in any stage of development
3. Working Software Delivery Frequently
4. Business and Development teams work together.
5. Build Project Around motivated individuals
6. face to face communication
7. Working Software
9. Sustainable development, The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
10. Continuous attention to technical excellence and good design enhances agility.
11. Simplicity is essential.
12. Self organized and motivated  and regular team reviews

Resource Leveling

Resource leveling as defined by PMBOK is a (project management) "technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply".

Resource leveling is a technique in project management that overlooks resource allocation and resolves possible conflict arising from over-allocation. When project managers undertake a project, they need to plan their resources accordingly.

This will benefit the organization without having to face conflicts and not being able to deliver on time. Resource leveling is considered one of the key elements to resource management in the organization.

What Teams Need from Project Manager

Direction-Setting

Context - Background information around the work 

Interface to Stakeholders 

Truth-Telling

Opportunities and Training

Access to Appropriate Tools

Work/Life Harmony

src - http://www.projectsatwork.com/content/Articles/293080.cfm

The study identifies five key steps for the execution of an effective knowledge transfer program:

1. Identifying: Determining what knowledge needs to be transferred
2. Capturing: Accumulating the essential knowledge that needs to be transferred
3. Sharing: Establishing methods for transferring the knowledge
4. Applying: Using the knowledge that is transferred
5. Assessing: Evaluating the benefits of the knowledge that is transferred

src - http://www.projectsatwork.com/content/Articles/292631.cfm

Effective Project meetings

1. Send out an advance agenda. 
2. Start promptly.
3. Never cancel. 
4. End on time.
5. Stay on topic.

src - http://www.cio.com/article/2896292/project-manager/five-keys-to-effective-project-meetings.html

3 main questions

1. What worked well in managing the project?
2. What didn't work well in managing the project?
3. What would we want to do differently next time?