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.
Disciplined Agile (DA) is a hybrid of existing methods that provides the flexibility to use a tailored approach that matches your context. In a nutshell, Disciplined Agile is “pragmatic agile”. This webinar explores how different business teams in an established enterprise apply Disciplined Agile strategies over time to successfully improve their own agility while also supporting the agile software delivery teams and the organization’s overall journey towards business agility.
Agile is still a hot topic. Started in the late 70s as an alternative to Lean Six Sigma, Agile become popular in the second decade of the 21st Century when Scrum became the de facto Agile delivery framework. Like most popular Agile frameworks, Scrum started as a software product development approach used by a small software development team to build new products. Scrum remains at the core of most Agile frameworks with the Scrum Master role being the flag bearer of any Agile Team. Nowadays, many projects have a software development component and a software development (sub) team. From the Project Management perspective, the Scrum framework doesn't handle some important project areas like Financial Management, Procurement, and Risk Management; therefore, a Project Manager is still required. The term "Agile Project Management" is widely used these days. Although, most of the time, it refers to small software implementation projects. This webinar is a comparative analysis of various aspects of a project from an Agile Perspective, attempting to define what differentiates an "Agile" Project from a standard project. The webinar will also address skills that the Project Manager needs to acquire or develop and practices that must be avoided when using an adaptive delivery approach.
Despite claims to the contrary, the need for governance does not disappear for agile projects. Your project sponsors have a right to know the status of the health and risk of their investments. But trying to blend traditional agile methods such as Scrum with traditional stage gate approaches can cause frustration for both project teams and their stakeholders. Disciplined Agile (DA) provides straightforward and common sense ideas for applying governance in a lightweight fashion for agile projects. This webinar explores these lean governance strategies using the Disciplined Agile tool kit.
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.
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.
The next generation of PMOs must adapt to meet the challenges of complexity and transformation. Adopting a new mindset and reconfiguring your PMO to make it lighter and more agile can help your organization expand its capabilities and provide significant benefits.
Question: Due to my special skill sets, I am often asked to move between teams, most of them virtual. Since each team functions differently (especially as we try to survive by being more flexible and responsive to the customer and also work from home), I find it difficult to remember how each team interacts and how to know the unspoken rules they use to run their projects and their online meetings. Is there any method that a team can use so that members, plus those of us who come in and out as needed, know how to adjust our behavior—and how they can standardize their own?
Choosing from agile versus traditional project approaches does not have to be a “black-or-white decision.” Hybrid approaches can help realize the benefits and set off the disadvantages of both agile and traditional approaches, particularly in complex environments.
Agile approaches tend to build resilience into the work because of the frequent build-release loop. But what if you can’t use an agile approach for some reason? Consider these three ideas...
Developing a project team that is ready and able to handle adversity as it arises is the only way to consistently produce results and achieve remarkable outcomes in these challenging, uncertain times. Here are tips and principles to help you build resilient teams.
An uncertain business environment is an ideal environment for agile delivery practices—the flexibility and adaptability encouraged by prototypes, continuous feedback and refinements. But there still needs to be clarity about needs, goals, and what ultimately constitutes success.
Ask a Question