Project managers need leadership skills—specifically emotional intelligence (EI)—to augment technical expertise. But agile thinking, leadership and EI skills are just one facet of project success. Businesses need to invest in project management processes that are agile to respond to the changing needs of the organization.
Connect In Person
All organizations, whether small or large, need individuals who understand how important and impactful adaptability and agility are to overall success. By attending this virtual event you will learn how you can help your organization embrace the opportunities in change, disruption, and transformation.
The PMI Talent & Technology Symposium 2018 is the fusion of two prior events, the Internet Systems & Technologies Symposium, and the Talent Management Conference. The new event focuses on the impact of rapidly changing technologies on the project management discipline and careers. Participants will better understand how emerging technologies affect their career and skills progression, as well as the evolving needs of hiring managers as they seek out top project management talent.
If you perform business analysis, your work is vital to project and program success. To most effectively support your organization and advance in your career, you need to know how to apply BA to any situation and delivery method. The new PMI Guide to Business Analysis will help you achieve this! Get an exclusive preview, with in-depth insights, at the PMI Business Analysis Virtual Conference 2017.
Hearing all the buzz about agile, wondering how you can get in the game? There are many ways to gain the benefits of Agile – from full on methodology to a hybrid approach. If you not ready to pick a method, but still interested in how you can use components of Agile, then this webinar is for you.
Hybrid project management has gained popularity due to its ability to effectively bridge traditional and agile methods. A major challenge faced by many Project Managers is knowing how to effectively plan, identify, and manage risks when using a hybrid approach.
The transition to Agile takes time and it is a significant cultural change. Skeptics needs to be convinced that Agile will deliver the benefits.This presentation proposes a new way of using the "traditional" project benchmarking approach adapting it to the specifics of an Agile Project Team.
Utilizing effective business requirements gathering techniques is crucial to project success in any environment. In RefineM’s webinar, attendees will learn how to effectively gather business requirements on Agile projects. They will be exposed to techniques including brainstorming, focus group techniques, and many other. They will leave the course ready to gather business requirements for Agile projects.
Project Managers will continue to play a vital role in the new Agile world. At the Enterprise Level there will always be a need for Governance and the larger the organisation, the more focus there will be in managing risks.
Podcasts and blog posts to help you manage the challenge of transitioning from traditional project management to Agile. Dave Prior celebrates success, embraces the learning that comes from failure, and digs deep on topics you need to be up to speed on.
In case you actually read this description, the beginning of the blog is about preparing for the PMP exam. It then evolved into maintaining my credential. After taking a break for a few years, I'm back and will be blogging about project management, in general, and probably a bit of agile on a regular basis.
The Agility Series focuses on agile and agility across the organization not just in software and product development. Areas of agility that will be covered in blog posts will include: - Organizational Agility - Leadership Agility - Strategic Agility - Value Agility - Delivery Agility - Business Agility - Cultural Agility - Client Agility - Learning Agility
This blog is a conversation between the Agile Practice Guide Team and our PMI and Agile Alliance Communities to gain insight, support and collaboration around the creation of a usable and relevant body of work that supports transition to hybrid and agile in project work.
Drunken Boxing for Project Managers “The main feature of the drunkard boxing is to hide combative hits in drunkard-like, unsteady movements and actions so as to confuse the opponent. The secret of this style of boxing is maintaining a clear mind while giving a drunken appearance.” Yeah... just like that… but with network diagrams and burndown charts… and a wee bit less vodka.
Save Time With Tools + Templates
This spreadsheet is an example of how to determine WSJF prioritization, as described in the article Prioritize Weighted Shortest Job First.
애자일 변환은 어디에서 조직의 가치를 극대화 할 것입니까? 비즈니스 환경이 급속히 변하는 지역이나 고객 또는 이해 관계자가 서비스 또는 제품의 지속적인 개선을 기대하는 지역 일 것입니다. 민첩한 접근 방식으로 가장 이익을 얻을 수있는 영역을보다 효과적으로 파악할 수있는 유용한 방법을 제시합니다.
This template provides a work breakdown structure for business intelligence projects and for requirement effort estimation for a waterfall methodology-based project or user story estimation for an agile-based project.
코치로서 올바른 통찰력을 얻고 코칭 참여 성공이 최적인지 확인하기 위해 비즈니스 환경과 고객의 문화를 평가해야합니다. 이 문서에는 코치가 조직의 여러 수준의 지도자들로부터 데이터를 수집하고 수집 할 수 있도록하는 두 가지 유형의 평가 질문이 포함되어 있습니다.
Learn From Others
When companies move to an agile Software Development Lifecycle (SDLC), they often remove the processes and analysis of their waterfall SDLC because, as the Agile Manifesto puts it, “They value individual and interactions over processes and tools.” Some of the rigor should be removed – waterfall processes can get bogged down with gates and sign-offs. However, caution must be exercised to not go too far against processes and analysis and rely just upon backlogs and user stories. Requirements and the analysis that leads to those requirements are just as essential in an agile project as they are in a waterfall project. The difference lies in how much requirements analysis is completed and the timing of it.
Many managers of distributed agile software teams struggle with time zones. Team members may also struggle with maintaining a traditional eight-hour workday when separated by multiple time zones. Perhaps it’s not the time zones that are the challenge; the real challenge lies in re-thinking the workday of the team.
The longer it takes to do anything, the longer the variance of task duration. When that happens, motivation and engagement decrease, and collaboration becomes harder to maintain. These effects build on each other in a vicious cycle. This is why technical agility matters.
One of the common complaints about traditional project management methods is that they collide with customers who don’t know what they want or keep changing their minds. Agile approaches can help, but you still have to manage the customer — and the requirements!
Weighted Shortest Job First is a widely used technique that can give guidance to the product owner as to how to prioritize the backlog in a rational way, supported by solid data. But if it is the only process used, it can lead to a mediocre priority list.
Saying the words “agile” and “scrum” does not make a company more agile and scrum. We need to build a safe and approachable community where open discussions can happen. Read about one practitioner's experience.
Our emotional intelligence gives us the confidence needed to trust and respect our emotional responses. Trusting and respecting emotions requires us to view all emotions as valid—while giving us the freedom to analyze if that valid emotion is truly applicable to our current situation. So, what can we do to trust and respect emotions?
If you can’t do “Agile,” you're not cool...right? Wrong. Agile approaches are wrong for some programs—and those alternatives are not strict waterfalls. Here, the author presents some ways to think about the kind of lifecycle that might be right for your program.
The agile coach is like an agile PMO structure. The purpose is like that of a traditional PMO—to ensure that the project creates the intended product within an acceptable time frame. What changes is the approach...
Has agile replaced other development methodologies as the go-to approach? Is it true for all projects? Let’s look at some characteristics of projects in the real world…
Ask a Question