IN THIS ISSUE Featured articles showcased in this issue: > When More Requirements Detail Is Advisable > Ambiguity, Uncertainty or Both? > Agile vs. Traditional... - Part III: Winning Through Integrative Thinking > When Less Requirements Detail Is Appropriate Webinar: Transform Software Delivery to Address Market Complexity and Change Webinar: The ‘who, what, when, where and why’ of Mobile Business Intelligence Also in this issue: > More Business Analyst Humor > Even more Resources for Business Analysts > New Interview Questions
FEATURED ARTICLES How Detailed Should Requirements Be? Part 3 - When More Requirements Detail Is Advisable by Karl Wiegers, Principal Consultant, Process Impact There are several situations in which recording only high-level requirements information increases the project’s risk. When you encounter situations such as the ones described in this article, expect to spend more time than average developing detailed requirements specifications. Read more...
Ambiguity, Uncertainty or Both? by Elizabeth Larson & Richard Larson, Watermark Learning We have always been fascinated by the exceptional business analysts who can create order out of total chaos. The ones who can ask those great questions, who can figure out what’s important and what’s less so, who can synthesize lots of information, put it all into their magic hat and come out with requirements that make sense to all the stakeholders. Read more...
Agile vs. Traditional... - Part III: Winning Through Integrative Thinking by Adriana Beal, MBA Instead of taking for granted that either you find a flavor of agile that will fit the needs of your organization, or you must completely dismiss the use of agile methods, a much more valuable approach is to determine, for each individual project, which agile concepts should be embraced or not. Read more... When Less Requirements Detail Is Appropriate by Karl Wiegers, Principal Consultant, Process Impact Several conditions make it appropriate to leave the requirements descriptions at a higher level of abstraction. Recognize that these are broad guidelines. The BA should perform a risk-benefit analysis to balance the potential downside of omitting important information against the effort required to include it. Read more... WEBINARS Transform Software Delivery to Address Market Complexity and Change On Demand - Register Now, Cost: FREE The ‘who, what, when, where and why’ of Mobile Business Intelligence On Demand - Register Now, Cost: FREE MORE FROM ModernAnalyst.com More Articles of Interest > Lean Six Sigma for non-industrial organizations > Requirements Reuse: the State of the Practice > The State of Business Analysis Practices in Organizations
DECEMBER 2011
Follow Us on Twitter http://twitter.com/ModernAnalyst
Got a Knack for Writing? We are always looking for quality content which is relevant or related to business analysis! Increase your exposure by submitting original articles to be published in the Modern Analyst eJournal. Send us an e-mail: [email protected] BA Webinars Increase your skills by attending one of our upcoming Web Seminars for business analysts. Your Thoughts? Your thoughts, opinions and comments to the editor are welcome and should be sent to: [email protected] Network with BAs Looking to network with like-minded professionals involved in Business Analysis? If yes, then join ModernAnalyst.com on LinkedIn and Facebook:
Business Analyst Humor
Did You Know? Did you know that you can create your own profile at ModernAnalyst.com? Showcase your skills, knowledge, and experience. Link to Us If you want to link to ModernAnalyst.com just copy the HTML code from the Link to Us page.
SUBSCRIBE: Subscribe to the ModernAnalyst eJournal! It's FREE!
brought to you by enabling practitioners & organizations to achieve their goals using: