business analysis
![]() |
Tips for Starting (and Ending) a Process Analysis Without boundaries, a process analysis could go on forever. Adapting things learned from working in agile software development, Scott Sehlhorst provides tips for starting—and ending—a process analysis. |
|
![]() |
There's No Such Thing as a Freemium Lunch The freemium business model—in which some users use the product for free, and others use it for a fee—can be appealing. To succeed with the freemium model, you must first acknowledge that a revenue plan is not a business plan and then decide if it makes sense for your bottom line. |
|
![]() |
It's the Relationships, Stupid Relationships—working and personal—are vitally important to successful business analysis. If you don't have them, nothing else much matters. |
|
![]() |
Is Your Data Deceiving You? Do you know how clean, accurate, and up-to-date your data is? Learn how to increase the quality of your data so that your data never deceives you again. |
|
![]() |
What Do Our Customers Really Want? Agile teams can create software quickly, but how quickly can they gather and process feedback from customers? Here is one team's experience, with some tips and resources to help you introduce a community of practice in your own organization. |
|
![]() |
Supporting Creativity for Real Business Results For Aspenware, supporting creativity is not only tied to real business results; it is also an important employee benefit, aiming to create an entrepreneurial environment that attracts the best local talent. |
|
![]() |
Are Your Requirements Flying Blind? Of all of the requirements a stakeholder says "must" be done, how do you know which ones "should" be done? Connecting the project vision and goals to the requirements can help your team decide. |
|
![]() |
Ideas for Eliciting Examples and Specifications In the past few weeks, I’ve been looking for ways to apply the techniques of pull conversations to getting specifications from our customers. Pull conversation techniques advise us to let go of our own assumptions and judgments and to try to put ourselves into our stakeholders’ world. |