Related Content
Confirmation Bias: The Most Human of Tendencies Confirmation bias is the tendency to notice evidence that supports our beliefs, preconceptions, and hypotheses, and to miss, ignore, or dismiss evidence that contradicts them. Instead of trying to falsify a hypothesis, we tend to try to confirm it. It’s a human thing to do. |
||
The Great PM and BA Debate The discussion of the relationship between the project manager (PM) and the business analyst (BA) is quite common, and some see a natural career path from senior BA to PM. The BA and PM roles are complementary—and there may be similar shared competencies—but there is a very different focus. |
||
Get Out There and Learn About Stakeholders' Problems One of the more often repeated phrases from the lean startup and customer development lexicon is the admonition to "get out of the building" in order to meet and learn about customers. What project teams should take away from this idea is the need to interact with stakeholders to address problems. |
||
Lean, Agile, Lean Agile—What's the Difference? Not everyone is going to embrace agile or lean, and even those who do often disagree on their overall definitions. The truth is that each method has its own individual meaning and benefit to your company. When you combine them, you truly maximize their potential. |
||
Why Some Teams Don’t Work There are teams that work well, and other teams that are so ineffective, merely being dysfunctional would be a step in the right direction. Naomi Karten explains the reasons why some teams don't work. The solution isn’t to dispense with teams but to figure out what makes them function effectively. |
||
How to Use Gamification for an Agile Transformation In a recent LinkedIn poll, the failure to change organizational culture was voted as the prime cause of preventing an agile transformation. One way to counter this problem is to use gamification, which leaders can use to encourage employees to make the transformation. |
||
Using Kano Analysis to Define Your MVP Kano analysis is a great tool for prioritizing the capabilities that you build into your product. It provides a great framework for competitive analysis, comparing products in the context of what actually matters to users and not just a list of checked and unchecked boxes. |
||
From Acceptance Criteria to Acceptable Product Using acceptance criteria to define an acceptable product works all the way up the stack from clarifying what the development team is being asked to do, to understanding what the users really need, to defining the minimum viable product that allows the company to achieve its goals. |