A friend of mine, Joseph Falhiff, just took the PMI Agile Certified Practitioner (PMI ACP) exam, and shares his immediate gut reactions to the exam on a live teleconference recording.
His co-host, Rory McCorkle, is the Product Owner of the exam. Rory gives us a brief update on the status of the exam and then Joseph goes into his experience with the exam.
Learn the SCRUM software development methodology in less than 10 minutes.
By the end of this fast-paced video, you’ll know about:
- burn-down charts,

- team roles,
- product backlogs,
- sprints,
- daily scrum
- and more…
Read More…
One of the traits of a great PM is their ability to communicate visually – presenting the progress of a project in a single glance so that one can see if things are going to plan or not. When you look at your world through visual lens that help you solve problems in business in new ways !
Edward Tufte teaches the gift of visualizing information in a way that people can take action on.
Agile teams often place large charts and graphs in their workspaces to radiate important information. It doesn’t matter if you are developing software, delivering IT infrastructure solutions, building a house, hardware products or systems – you can visually see if you project is on track or not.
Burn Charts
Agile teams often track project progress through ‘’Burn charts’’ (burn-up, burn-down and cumulative flow) which are a very popular way to give visibility into a project’s progress. Burn Charts are a graphical representation of the work left to be done and of the progress that has been made. The chart is typically drawn to show progress against predictions.
They are extremely simple and astonishingly powerful. They reveal the strategy being used, show the progress made against predictions, and open the door to discussions about how best to proceed, including the difficult discussions about whether to cut scope or extend the schedule.
Back by popular demand…Join us at this 1 hour live coaching session where Birgit Zacher Hanson, author of Who Will Do What by When? will reveal how to change the accountability game and make it winnable. Birgit will also answer questions in real-time while coach participants on real-life-issues that relates to getting others to commit and follow-through.
Birgit helps corporations with the following – she can help you too !
- Strengthen leadership capabilities and help leaders develop coaching skills that lead to sustainable excellence
- Build collaborative teams and work cultures that enable superior project execution in alignment with business strategy
- Empower individuals to fulfill on their potential and reach new levels of success
Can you make people do anything they don’t want to do?
Holding others accountable is a myth. It’s like Sisyphus being condemned to pushing the rock up the hill… It’s exhausting. If you are a manager whose job it is to get a team to work together and get the job done, this may be bad news. I am sorry.
I know it can be extremely frustrating when nothing you say or do seems to make a sustainable difference with some people.
You can micromanage, push, scold, even threaten certain people and get what you need for a little while, but as soon as you turn them loose, the rock rolls downhill again. And you start over, doing the same thing you have been doing – pushing, scolding, complaining like a broken record.
Read More…

I must agree that all my projects that leverage Agile practices produce Customers and Employees that are much more ENERGIZED and ENGAGED. By continuously releasing features and functionality – your project stays “top of mind” and “talked about” with your sponsors and customers.
A great example would be several of the projects in my current program where we have created a prioritized backlog of features we believe meet our customer’s needs. Which was done after a 2-3 month planning and analysis phase that outlined the resource, budget, technology, and architectural needs for our sponsors.
We are now putting a release roadmap together for iterative releases on a 4 week cycle. And the developers and testers are using daily standups during each iterative development cycle to keep a handle on progress, obsticles, and continuously adjusting the backlog for future releases.
A great article I read this weekend talked about the 5 Reasons Agile is much more important than being Perfect for being innovative, including:
1. Speed Wins
2. Perfection equals 2nd place
3. Who’s perfection is it anyways
4. It energizes your employees
5. It energizes your customers
Click here for the full article on OPENForum