Lean governance is a term that is being thrown around a lot, but what exactly does it mean? And is it important for the future of PMOs? Yes, but the challenge for PMOs might be in creating the environment where they can leverage lean governance.
For some agile teams, especially software development teams, the term "Change Management" is associated with the ITIL style Change Control, an engineering process created to manage risks associated with production deployment. Despite the optimistic view presented by most agile frameworks, Organization Change Management is hard. The transition to agile is often harder than any other transformation because it requires a mindset change at all levels, supported by a huge shift in the organizational culture. This webinar is a practice-based presentation on the importance of Organization Change Management in Agile Transformations and the critical role that the Project Manager must play.
Since the term, agile, grew popularity in the second decade of the 21st century, Risk Management was one of the strong selling points of various agile frameworks. According to agile surveys, reducing risk is one of the main reasons for agile adoption. However, none of the agile frameworks provide guidance on Risk Management. Most of them are limited to a simplistic view that by delivering in small increments risk is limited to the value of a single sprint. The reality is far more complex, and it is not limited to coding or technical skills. A project is dependent on context, on organizational culture, and last but not least, on people's desire to work as a team and succeed. This webinar is a brief introduction to how important Risk Management is, how it can be done in agile, and why risk, especially in Agile, should not have a negative connotation. Real-life examples will be used to illustrate how the Project Manager, Scrum Master, and the whole project team can take advantage of Risk.
Agile found its way into project delivery with many certifications trying to define various Agile project roles. Most Agile frameworks, such as Scrum, Crystal, and XP, were conceived by developers for a small team of software developers, and the Project Manager role is usually omitted. Unlike some specialized Agile Project Manager certifications, PMI's Project Management Professional (PMP)® remains the benchmark for the Project Manager role with an increased focus on Agile and Hybrid practices but without compromising the predictive knowledge required to manage projects that can't or won't use Agile practices. This webinar is a comparative analysis of the Scrum Master, seen in some organizations as a replacement of the Project Manager role; various flavors of the ‘Certified Agile Project Manager’; and the standard Project Manager role.
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.
This blog explores pragmatic agile and lean strategies for enterprise-class contexts.
This blog concerns itself with organizations moving to business agility—the quick realization of value predictably and sustainably, and with high quality. It includes all aspects of this—from the business stakeholders through ops and support. Topics will be far-reaching but will mostly discuss FLEX, Flow, Lean-Thinking, Lean-Management, Theory of Constraints, Systems Thinking, Test-First and Agile.
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.
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.
To truly achieve business agility, organizations must ensure their underlying operating systems support it. Six areas are crucial to success: leadership and management; culture; structure; people and engagement; governance and funding; and processes and practices.
Swarming is a method that agile teams can use to improve prioritization, collaboration, learning and overall delivery. Here’s a look at how it works—and how you can benefit from using it on your teams.
A high-performing agile team requires the development of a positive attitude. Here are eight steps to help you and your team cultivate a positive mindset, from vision, rules of engagement and buy-in, to accountability and celebration.
Sprint/task boards can be the key to success when you're managing remote projects. But what if you don't have access to fancy ones? Here is a brief summary of sprint/task boards, including what they allow you to do, how the process typically works, and a DIY solution.
Every organization expects its projects and processes to be agile. However, somewhere along the way, we end up going through rituals without actually implementing agile principles into our processes.
Various project management approaches employ terms and concept with their own specific meanings; much time has been spent on trying to create a common language among them. It would be better to focus on a common understanding, adjusting our language to our audience.
On a distributed project, the team can’t rely on the informal, incidental information-sharing that occurs when we’re roaming the same hallways or going out for lunch. That’s why an intentional communication strategy is needed to keep everyone informed and involved.
The hyper-agile software development lifecycle is an end-to-end process for developing and delivering applications using citizen development.
La próxima generación de PMO debe adaptarse para enfrentar los desafíos de complejidad y transformación. Adoptar una nueva mentalidad y reconfigurar su PMO para hacerla más liviana y ágil puede ayudar a su organización a expandir sus capacidades y brindar beneficios significativos.
Ask a Question