Project management methods have tended to be too complex to be easily understood and applied by non-experts. The pivotal assumption has been that documenting every aspect of a project in detail will provide a high level of control of the planned activities during the implementation of the project. Many project managers ended up producing massive numbers of documents and swathes of paperwork, leading to an overall feeling that the role was primarily administrative. In contrast, widely used management disciplines are often linked to a few simple frameworks that can be easily understood, and applied, not only by managers but also by the majority of individuals. Porter’s Five Forces and value chain analysis help to make strategy a key area for every organization to apply.
92 items found
There are many problem solving methodologies-from TRIZ to OODA, from RPR to GROW, but this session won't discuss any of them. Instead we're going to focus on simple, standalone strategies to improve our problem solving effectiveness regardless of our existing PS skills or experience.
Statistics show that globally about 33% of the food produced in the world is lost or wasted. On the other hand, we have about 11 % of world suffering from malnutrition and hunger. According to UN based WHO, even if 25 % of the food wasted is saved then it can alleviate the hunger problem. The problem is acute and is obvious but yet organizations and people have not come to grips with it. Thankfully, during the last few years the situation is changing.
The purpose of this presentation is to summarize and share the strategies, planning, and execution lessons learned from a large scaled Windows 7 to Windows 10 migration project at a large Health Care provider organization. The author will share the challenges presented, and the tactics and techniques developed and implemented by his team to complete the project on schedule and on budget. This is not an instruction guide on how to plan and execute a Windows 10 migration project. This presentation simply shares their lessons learned and best practices with the hope that the audience can harvest one or more point to apply in any future desktop operating system migration project.
The process of project management is the process of making decisions. Much of our thinking about how to make decisions reflect an ideal generally called rational economic actor. In an ideal world, you weigh the alternatives based on reliable data, compute the most advantageous path and decide to choose that course. We maximize the expected economic outcome given some set of constraints. Ideally, we do this in a timely manner using a process that is transparent and inspectable. Everyone involved can understands why that particular decision was made. In the messy real world, we down-select the alternatives to consider. We work with limited data, fuzzy or even inaccurate data and, frequently, decide to take the path of least resistance. Getting to better decisions requires some planning well before the decision is to be taken. Increasingly we acknowledge the role our inherent biases play in our decisions. The insights of behavioral economics allow us, up front, to design decision making strategies and processes which limit the role of our cognitive biases. No process will immunize us against all failures but knowing what to look out for increases our success rate. During this talk we will examine how to increase the chances that our decisions will actually advance our project’s objectives without being stick in analysis paralysis. We will discuss how to make your decision making more aligned with your goals and make those decisions quicker and more reality based.
Per the Agile Business Consortium, business agility allows businesses to adapt quickly to market changes; respond rapidly and flexibly to customer demands; adapt and lead change in a productive and cost-effective way without compromising quality; and continuously be at a competitive advantage. The primary reason for moving to Agile is to achieve faster business value and keep you ahead of the competition. Agile is built for change - fundamentally, it is about creating Business Agility. It enables the enterprise to deliver projects more efficiently, with relentless focus on business value and providing the highest return on investment. Whether it is a software project, a new service offering or a new product, Agile’s twelve principles and three pillars (transparency, inspection, adaptation) are designed to reduce money spent on undesirable or unusable features which were built based on outdated requirements.
Coordinating Knowledge Work in Multiteam Programs: Findings From a Large-Scale Agile Development Program
Software development projects have undergone remarkable changes with the arrival of agile development approaches. Although intended for small, self-managing teams, these approaches are today used for large development programs. A major challenge of such programs is coordinating many teams. This case study describes the coordination of knowledge work in a large-scale agile development program with 12 teams. The findings highlight coordination modes based on feedback, the use of a number of mechanisms, and how coordination practices change over time. The findings can improve the outcomes of large knowledge-based development programs by tailoring coordination practices to needs over time.
Where should you use Scrum and where should you use Kanban? Many factors weigh into this decision, including whether your teams are in development or maintenance mode and whether their work is highly predictable or sporadic. Attendees of this webinar will come away with a better understanding of Scrum and Kanban and when to utilize each, together or separately, to improve agility of their teams.
Digital Transformation is the #1 priority for boards and CEOs. It's a $1.7 trillion industry in 2019. And yet 70% of all digital transformations fail. Why? And what can a project manager do about it?