The damaging consequences of organizational amnesia, and how BAs can help prevent and remediate them

From the Modern Analyst blog

http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/3822/The-damaging-consequences-of-organizational-amnesia-and-how-BAs-can-help-prevent-and-remediate-them.aspx

Imagine that a business analyst has been assigned to write the requirements for a new system replacing the company’s legacy CRM (customer relationship management application).
After mapping out the as-is process at a high-level, the BA’s stress level starts to go up. “There are three complex modules in this system, and so many details about the as-is state that I still don’t understand! The legacy system barely has the original requirements documented, with plenty of change requests implemented later without proper documentation. How am I supposed to finish my deliverables on schedule and without mistakes given my limited knowledge of how the system being replaced works?”

14 Financial Analysis Approaches the Business Analysis Professional Should Know

From the BA Times blog

http://feedproxy.google.com/~r/BusinessAnalystTimes-BusinessAnalysisHome/~3/PEKqBffmyeM/14-financial-analysis-approaches-the-business-analysis-professional-should-know.html

14-financial-analysis-approaches-the-business-analysis-professional-should-knowWritten by: Richard Lannon

It is not often that I write about numbers. Why, because some professionals find it boring and want to nod off at the mention of numbers, while others simply say, well my numbers are giving to me by someone else.

Why DevOps Still Needs Release Management

From the CM Crossroads blog

https://www.cmcrossroads.com/article/why-devops-still-needs-release-management

Release management

Release management is still critical in a DevOps environment. You likely will just have to change your current process. You will no longer need to track implementation or back-out plans as part of change orders; you just need to be able to track the application, its components, and its promotion schedule. The key to maintaining these change orders is automation.

The Elevator Speech… for the BA

From the Modern Analyst blog

http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/3869/The-Elevator-Speech-for-the-BA.aspx

A BA walks into an elevator, is joined by an executive, and suddenly the executive asks the BA, “So, what are you working on these days?” (Sounds like the start of a joke …)  Most business analysts, due to their project success focus, think of requirements management when questioned about their work. So the BA responds by describing the features of a business solution that the BA is currently working. The BA seldom mentions the associated business benefits with the work (i.e. why the work is vital to the business). Unfortunately, the BA ignores the first rule of conversation: know your audience. The executive asking the question is more likely to understand and be interested in the business value provided by the work, rather than the solution features.

Overcoming the Hurdles of Continuous Delivery: An Interview with Jeff “Cheezy” Morgan

From the CM Crossroads blog

https://www.cmcrossroads.com/interview/overcoming-hurdles-continuous-delivery-interview-jeff-cheezy-morgan

Jeff "Cheezy" Morgan

In this interview, Jeff Morgan, the chief technology officer and cofounder of LeanDog, explains how continuous delivery and continuous deployment have changed how software teams do business. He breaks down funding projects versus teams and validating quality as you build your product.