Managing organizational change is one of the big, hairy elephants in the room when we manage projects. It is one we all recognize and know about, but that we struggle to deal with effectively--or even sometimes to discuss. Why this is, and why this should be, is a bit of a mystery.
What happens to a PM who is trying to adopt Agile? Dave Prior, PMP discusses the struggles you can expect to encounter while showing you how creating a Personal Agility Canvas tool can help make things a little easier.
Epistemology is a branch of philosophical and scientific inquiry that asks “how do we know what we know?”. The speaker is amazed how little this is asked in the majority of books, research papers and industry studies related to project management. The speaker will argue that this lack of inquiry and understanding is the cause of many project failures.
Learn From Others
Our webinar Enterprise Agility Starts with Healthy Teams, How Healthy is YOUR Agile Team? with Sally Elatta was incredibly popular. Here she offers advice based on your questions that she was unable to address during the session.
The alternative to embracing change doesn’t have to be completely rejecting it. Are there ways we can introduce more flexibility to waterfall projects without losing control of change? Can traditional project execution approaches learn anything from the agile approach to change?
Project management in construction follows traditional planning methods to communicate project schedules. The objective of this article is to show how agile tools like burnup and burndown charts help communicate project timeline and progress.
Agile methods recommend co-location and face-to-face communications, but studies of office workers show high levels of dissatisfaction with open-plan environments. So, how do we make agile work and minimize the issues surrounding open-plan environments?
Is agile working for your team? Do standups feel like micromanagement? Are people missing commitments because they are spread across projects? If people are going through the motions of agile and aren't happy about it, use these five key questions to help.
Did you know that agile has an explicit and core principle guiding decision making? You can’t be agile without following it. It’s called “deferring decisions to the last possible moment."
Kanban has become popular in the software development world--but is used very selectively. Developers are missing real opportunities to better serve customers in both software operations projects and in new development projects. Here we cover the core principles of Kanban that can be applied to any project where improved quality and throughput are desired.
You’re a hardworking, successful business analyst (BA), and have just been told your organization is “going agile.” Perhaps you’ve heard a few details about the types of roles involved in an agile development environment, but nothing that really depicts how a BA fits into this new atmosphere. So what does this shift in your organization mean for you?
The number of agile certifications available in the market keeps growing, and one must consider the unique needs of the inquiring company or individual to know what would be best for them. What factors should you consider? Do you even know the options available?
Managing quality during a software development project can be difficult and time consuming when you have been misinformed about true quality indicators and practices. Actively managing quality on an agile project can be both simpler and harder than traditional approaches. Here are some basic practices to save time and unnecessary rework--and improve stakeholder satisfaction before and after delivery.
Ask a Question
|NPD Governance||Dale Wolaniuk||May 13, '15 8:46 AM||5||5|
|Mark All Read|