Related Content
What to Do When Your Project Slips If your project has ever slipped, you are most certainly not alone. Naomi Karten lists the reasons that lead to a broken project or one that has fallen behind, and describes what you can do to avoid catastrophe. |
||
Reconsidering User Stories User stories, one of the most common agile techniques, are used by delivery teams to support their iterative planning efforts and are typically used to represent items in a backlog. Until recently there has been a general agreement about the form that user stories should take. |
||
Resilience and the Softer Side of Business Analysis Business analysis is a wide and varied discipline that relies on the practitioner's honing and developing skills in a number of areas. Adrian Reed looks at an important business analysis attribute that is rarely talked about—resilience. |
||
User Story Mapping—Goal-Driven Backlog Development When product managers plan what product releases will include, the goal is to deliver value for the users. Every release of a product should make it better than the previous release. User story mapping is a technique for assuring that each release or iteration makes the product tangibly better. |
||
Measuring Development Time: Not the Best Way to Spend Your Time Managers and project managers are often obsessed with measuring the time it takes to do a task. Time is useful to consider, but measuring time doesn’t always give us the information we really want or need. It's true that work takes time, but it's more valuable to measure results and value delivered. |
||
How to Bring Requirements to Life A key skill of the business analyst is to elicit and analyze requirements and to help stakeholders consider a range of possible solutions. Because abstract and logical requirements are extremely hard to digest, Adrian Reed offers concrete ideas on how you can bring requirements to life. |
||
Are You Experiencing Product Manager Insomnia? What should be keeping you awake is what keeps your customers awake. Remember to be market-driven and to focus on the problems that your customers value—and are willing to pay to solve. |
||
Clean Language in Business Analysis Clean Language originated within the discipline of therapy and focuses on understanding other people’s personal metaphors. It can help business analysts to form better questions and prevent inadvertently leading or pre-supposing a solution. |