Agile testing is commonly mistaken as only referring to the Quality Assurance/testers on the team. This is a destructive, limited view of this critical agile development piece. This article places the emphasis on the often neglected, misunderstood and essential collaboration tool.
Advance Your Career
In this unrehearsed call, Joseph Flahiff will coach Liza Wood through the issue she decides to bring. Joseph has done no preparation, and does not know the problem that Liza is going to bring. This is just what it is like when team member comes to a coach for a 1:1 session.
Agile PM is one of the emerging ‘hot topics’ in the PM domain, and given the breakdown of the ‘plan – then execute’ model in Project Management, the adept project manager is constantly having to improvise to deliver against changing project deliverables. This webinar considers and compares Agile PM and Organizational Improvisation, and offers assistance with moving PM execution from the ‘tools and techniques’ based PMBOK® model towards techniques better equipped to deal with today’s ambiguous and changing project environments.
Save Time With Tools + Templates
The Risk Management Grid is a technique to identify potential risk events that could impact one of more of the project’s Seven Win Conditions. Importantly, it also serves to decide how those events will be prevented or mitigated.
The Three-Sentence Project Skinny is a concise summary of the purpose of the project. It addresses the what and the why.
You can't do everything, nor should you. This template helps you figure out what is in and what is out of your project.
These are the do-or-die, must-meet requirements in order for the project to be considered a success. As such, they are continuously focused on by the project manager and core team.
Win Conditions address how success will be measured. How do you stack up when it comes to stakeholder satisfaction, your schedule, scope, quality, budget, ROI and team satisfaction? This template helps you rank priorities, and provides areas for metrics and descriptions.
Learn From Others
In attempting to make agile methods scalable, it is tempting to add more process to assist larger-scale coordination. However, that is the last thing we should do. Scaling collaboration, not process, is the key to enterprise agility.
This is the final article in a three-part series on the factors to consider when determining whether an organization, team or project is “ready” for agile. This third installment continues the discussion by examining factors that are specific to the project itself and whether it is really suited to an agile approach.
Can agile teams--even high-performing ones--burn out? Of course. Far too many teams seem to schedule their sprints sequentially or back to back, without a pause or break. So if you are suffering from burnout, what are some helpful techniques to refresh and recharge your teams?
This second article continues the discussion by looking at the second group of factors related to the readiness (and willingness) of the project team to adopt agile best practices. As with sponsorship factors, we need to consider cultural, structural and management aspects.
Many organizations have struggled with their early agile experiments. Due to the issues faced, they typically cannot answer the simple question: “Are we ready to go agile?” This first article examines the factors that indicate whether the sponsoring organization is ready (and able) to modify the way it works to increase the chances of a successful agile project.
Most of us work on projects where we know the end date or the budget--or both. But there is a category of projects where we might not know either: emergent projects. Emergent projects are change projects such as your agile transition or any other project that you have no control over. Can you apply agile to those projects? Yes. Carefully.
Project teams quite often assume that the product manager is a true partner--and when a project is under scrutiny or stress, the product manager can transform into a very tough adversary and oftentimes a combative stakeholder. Put yourself in a product manager’s shoes for a change! Let’s explore a couple of myths about product managers that should hopefully spark a new level of collaboration and success…
Being nice is not a courtesy or even a basis for competitive advantage anymore. In today’s connected workplace with a less loyal and more mobile workforce, the economics of compassion are very real. See what smart companies are doing to recruit and retain the best talent.
Every aspect of product development can be done better or worse. That includes being a team player, writing code, communicating requirements, testing functionality...you name it. But how do you ensure that people do the best thing? And, can you even do that? That is, can you somehow force good practice? And what can you expect to happen by doing so?
It is a practical approach to understanding why decisions are so complex and what can be done about it. In order to create the combination between top-down problem decisions (waterfall-like approaches) and local problem decisions (agile-project approach), here are three practical guidelines.
Ask a Question
|can anyone recommend a project management tool for managing Agile projects?||Sanjay Lala||Oct 22, '14 3:49 PM||1||1|
|What Metrics does your PMO request?||Joseph Flahiff||Oct 17, '14 2:11 AM||4||4|
|Mark All Read|