Project teams have a lot to deal with on projects. They will have to navigate multiple problems, such as risks becoming issues, costs exceeding budget, and schedules slipping, on any given project. The top notch project managers and teams are skilled and experienced at coming up with innovative solutions to these problems. How can any project manager or team acquire this skill? In this post, we describe five ways to improve creativity on project teams to foster project management innovation. These steps range from building the foundation through organizational structure and culture to trying out agile practices.
Project management processes can be implemented with only simple tools that project managers and team members are likely to have, such as templates for Microsoft Office programs or Google Docs. For some project managers and teams who have grown out of Microsoft Office, a software tool may be useful. Many tools are available on the market for teams or companies of various sizes, and some are also cloud-based for ease of access by everyone on the team.
Is your organization thinking about implementing Agile? Agile can provide numerous benefits to any organization, but the implementation process is not always smooth. This post is for change leaders or executives who are thinking about implementing Agile in their organization, but are not sure if the organization is ready yet. Before investing in training or resources, make sure these five things are in place; otherwise, it may not be worth investing resources in training teams yet.
Project managers need to develop strong habits to be highly effective. Based on Stephen Covey’s landmark book, The Seven Habits of Highly Effective People, we recommend five habits for project managers to develop in order to become, and remain, highly effective.
One of the key measures of a project management office (PMO) should be whether project delivery capability improves as a result of its existence. The PMO contributes to successful project delivery by providing standards for project management, empowering the organization’s project managers, and increasing the visibility of project management. To accomplish these key goals and remain relevant, PMOs need to be dynamic and proactive rather than static and reactive.
According to PMI’s 2016 Pulse of the Profession report, organizations lose $122 million on average for every $1 billion spent on projects, an increase from the last measure in 2014.
Although the waste could be worse, organizations should examine ways to further reduce that waste. PMI’s (2014) recommendations for minimizing these losses include greater coupling of projects with organizational strategy and a greater organizational agility that includes more emphasis on customers and processes. In this blog post, we will provide commentary on both the 2014 and 2016 reports and offer additional solutions from the perspective of our project management experience.
How do Agile methods differ from waterfall methods? In this blog post, we will answer that question and we will present the key differences between Agile and waterfall. As the traditional method used to deliver projects, waterfall tends to be the more common and generic way of managing projects. Agile is typically used with software projects, but can also apply to other projects. Depending on the type of project, Agile may or may not be a good fit for non-software projects. With other types of projects, you might even be able to integrate Agile and waterfall methodologies together to create a dynamic way of approaching a specific project.
The business analyst (BA) and the project manager (PM) each fill critical roles on projects. Business analysts lead requirements gathering, solutions generation, and communication with business users, while project managers lead the project from initiation and planning to executing, monitoring and controlling, and closing. Many times, there is overlap between the business analyst and project manager roles, and the roles and responsibilities of each title may vary between companies. With these factors in play, how can a business analyst transition effectively to a project manager role?
This is the second post in a Q&A series with RefineM’s CEO and founder, NK Shrivastava. In this post, we’ve asked NK to share his experiences with Agile, and why he believes Agile is an important aspect of project management. If you’re interested in reading the first interview in this series, take a look at Q&A with NK: Beginnings in Project Management. We hope that you will be able to learn more about NK and how his career has helped shape him into an excellent Agile Coach and the CEO of his own company.