IN THIS ISSUE
Featured articles showcased in this issue:
> How Detailed Should Requirements Be? - Part 1
> How to Effectively Engage Requirement Contributors to Achieve Project Success
> Agile vs. Traditional: Methods are a means to the end, not the end themselves
> Business Rules: Basic Principles and Pattern Questions for Business Analysts
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
How Detailed Should Requirements Be? - Part 1
by Karl Wiegers, Principal Consultant, Process Impact
Recently I was chatting at a wine tasting event with a couple of lawyers, who I had just met. One was surprisingly inquisitive about my work in the software requirements arena. Apparently she was working on case involving software at that very time. At one point she asked me, “How do you know how detailed to make the requirements?”
How to Effectively Engage Requirement Contributors to Achieve Project Success
by Matthew Leach, Doreen Evans Associates, Inc
Your new system just went live and the project, that replaced a critical legacy system, is coming to a close. Business analysts gathered requirements and worked closely with users and developers, but did you capture all of the requirements?
Agile vs. Traditional: Methods are a means to the end, not the end themselves
by Adriana Beal, MBA
By taking a closer look at how your company is developing software, and what is working for projects with different profiles, it’s possible to leverage winning strategies and hybrid approaches to make your software initiatives equally or more successful in the future.
Business Rules: Basic Principles and Pattern Questions for Business Analysts
by Ronald Ross & Gladys Lam, Business Rule Solutions, LLC
Before harvesting business rules, you should be aware of some basic principles and absorb them into your practices. First, all business rules are subject to change, including (and perhaps especially) business rules derived directly from business policies. The ability to change and redeploy business rules is essential to business agility.
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
> Classifying Decision Model Structures
> A Proposal for an Agile Development Testing V-Model
> Introducing RuleGuide™ - Business Decision and Rule Management
> Iterative Analysis and the Diminishing Business Strategy
> Systems Thinking: Understanding the Whole and Not Just the Parts
> Breaking Through the BA Mystique
Relevant Interview Questions
> What is The Agile Extension to the BABOK® Guide?
> Describe Pareto Analysis and how is it used.
> What is the Agile Manifesto?
FEATURED Business Analysis JOBS
Hewlett-Packard State & Local Enterprise Services, Inc. is accepting resumes for Business Analyst in Frankfort, KY. (Ref. #SLFRABA11). Research, elicit, analyze, validate and document business requirements, and to ensure that requirements clearly reflect true business needs, correctly representing all stakeholders. Mail resume to Hewlett-Packard State & Local Enterprise Services, Inc., 5400 Legacy Drive, MS H1-6F-61, Plano, TX 75024. Resume must include Ref. #SLFRABA11, full name, email address & mailing address. No phone calls please. Must be legally authorized to work in the U.S. without sponsorship. EOE.
> Requirements/Change Management Analyst Job
> Business System Analyst Job
> Business Analyst (Marketing Analytics)
> Strategic Pricing Analyst
> Project Manager/Business Analyst
More BA Jobs...