Wonder Club world wonders pyramid logo
×

Reviews for Project Management

 Project Management magazine reviews

The average rating for Project Management based on 2 reviews is 4 stars.has a rating of 4 stars

Review # 1 was written on 2017-07-14 00:00:00
2005was given a rating of 5 stars Eileen Prebensen
Takeaways from reading the book: Part 1: Define the project. Pages 33, 35, 76, 297, 340 - What is the goal of the project? What is to be done? Example: Make a lunch pill. - Why is this to be done? What is the purpose? Example: To save time preparing and eating lunch. - Who has which needs? Example: Users may need to satisfy hunger, save time and/or reduce weight / keep weight down. - Measure expectations as precisely as possible. Project phase 2: Design the project process. Pages 33, 35, 80, 86, 107, 110, 136-138, 159, 254, 393 - What concrete tasks will be done? Simplify tasks as much as possible. - Who will do which tasks? The fewer people involved, the less complex. When people come together to form a team, try discovering the values of each person. - When can which tasks start? - How long time will which tasks take to do? By simplifying tasks, duration of sprints can be shortened. - Which tasks can first start when which other tasks have finished? In other words, to what extent does the start of one or more tasks depend on the finishing of another / of other tasks? - Which tasks can be done in parallel / during the same period? - What does it cost to do the project? - How much money can we save / earn by doing the project? - What is the shortest possible project duration? What is the lowest possible cost? What is the highest level of quality that can be achieved? Which of these - time, cost, and quality - has the highest priority when? Project phase 3: Manage the project on a daily basis. Pages 33, 35, 86, 164-167, 209, 257, 271-273, 293, 300, 340, 368. - Set goals with people. - Say no to non-goal-achieving tasks, tasks that do not add value. - Continuously keep project plan up-to-date Use, for example, and/or - Continuously communicate openly about what is going on - including results of sprints. Use, for example, Twitter, blogs, and/or other social media. - Constantly do what is most important. That includes continuously prioritizing between time, quality, and cost. - If a mistake is made, fix it immediately and move on. Look ahead. - Continuously serve project workers as well as possible. Listen to what people need. - Continuously give people, who are involved, feedback. - Learn constantly the way you learn the best. - Facilitate meetings when needed. - When problems happen, find the reasons and solve them. - Solve conflicts. - Celebrate reaching goals. Project phase 4: Improve products and processes continuously. Pages 33, 35, 162, 293, 340. Examples of questions to ask: - What products do users like? - What do users and other project participants like about the process? What should we continue to do? - What is getting in the way from doing the project faster? - What do we need to stop doing to create more value for more people? - What do we need to start doing / start testing / start trying out?
Review # 2 was written on 2013-07-03 00:00:00
2005was given a rating of 3 stars Ned Hill
Good content but most of it was just from PRINCE2.. May as well jus buy that!


Click here to write your own review.


Login

  |  

Complaints

  |  

Blog

  |  

Games

  |  

Digital Media

  |  

Souls

  |  

Obituary

  |  

Contact Us

  |  

FAQ

CAN'T FIND WHAT YOU'RE LOOKING FOR? CLICK HERE!!!