Sprint goals provide focus and direction to the team. They must be specific, meaningful and manageable, so the team understands what is and isn't included, what value they are delivering, and how success will be determined. Here are four common issues with sprint goals and ways to avoid them.
Connect In Person
Help us celebrate this event's 5th anniversary! The PMI® Organizational Agility Conference returns bigger and better than ever as we examine evolving approaches to resilient value delivery! To remain relevant in the VUCA world, organizations and delivery professionals need to build change resilience—the ability to remain in a state of change while delivering value. This virtual conference will explore the concept of change resilience with professionals who are driving it within their organizations—and those who are living it as part of their own development.
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.
In an agile world, team members are empowered to make important decisions within the context of the behavioral architecture, without having to ask permission from supervisors or managers. But these supervisors and managers are coming from a lifetime of learning how to succeed in a hierarchical world, so they will need to leave behind those ingrained lessons. In order for agile to be successful at scale, leaders will need to change.
According to some practitioners, Agile was initially developed as an alternative to Lean. In the late 1980s, companies realized that achieving perfect quality, the elusive Six Sigma 3.4 defects per million opportunities, is not enough for a product to be successful. Meeting the customer needs, or perceived needs, on time became at least as important as good quality. Agile started as a production development approach, where creativity plays an important role. In later years, it is used in projects and outside IT or manufacturing domains. This webinar presents the challenges in implementing Agile in Lean organizations and also introducing Lean practices to Agile teams, balancing excellence with flexibility and creativity.
Agile is perceived as a better way of delivering projects, products, and services. Unlike the traditional approach of measuring the value delivered based on the planned deliverables, the budget spent, and meeting the critical milestones, Agile doesn't provide clear metrics that can be used to compare projects and delivery teams. Agile is a new approach, and traditional project benchmarking may not be relevant.
Agile Project Management requires some additional skills to be possessed by an Agile Project Manager. It does not only involve managerial skills but also requires more team-oriented and leadership skills. Agile Development is a value-driven model with focus on outcomes unlike traditional approaches which are plan-driven in nature and based on output.
With the proliferation of cloud-based self-service platforms, it is becoming increasingly commonplace for business to break free from the shackles that bound them to Information Technology (IT) strategy forever. While strategy is never a bad thing, it can be the slow-moving tanker that takes forever to change course, and in the age of agility, most companies have not aligned their strategy with agile principles, even less so IT. Shadow IT, as it is known, has many advantage. But it also creates many challenges.
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
Agile project leaders and teams can use this one-page worksheet to help plan and create sprint goals, including description, demonstration items, Definition of Done, and key metrics. Use in conjunction with the article Sprint Planning: Are You Doing It Backwards?
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.
We all know that agile is about delivering valuable solutions to customers, but is that actually happening in your organization? Do you even know the answer to that question?
Teams will say that they need to learn how to say "no" more often. Actually, they need to learn ways to decline requests in a positive, productive manner. Here are five recommendations for teams to both properly support their stakeholders while also defending their own productivity.
Adaptive strategy is sometimes a response to fast-changing environments—and sometimes it’s just chaotic reaction. Here's how to use agile techniques to tell the difference between the two—and still achieve great outcomes.
In more and more software development environments, there is a shift occurring from project-focused work to product-focused work, which is resulting in the creation of “permanent” agile teams. The implications are far-reaching. Let's look at two areas: the backlog and team behavior.
Colonel John Boyd discovered that the primary determinant to winning aerial dogfights was observing, orienting, planning and acting faster. How does this apply to project management?
The need for prioritization appears when multiple projects are planned in an organization and there is a shortage of resources. In order to deliver business goals and objectives, the focus should be on projects that provide strategic value. Learn about the factors and methods involved to better prioritize your projects.
Like many fields, nonprofit and government organizations want to find ways to respond to projects faster and more efficiently. This article provides five ideas for them to use agile methods and approaches.
Ask a Question