Tip of the Week
Sign up for our free Business Analyst Tip of the Week:
Tags
Agile analyze BAcareer balanced scorecard BAskills BAteam business architecture business drivers business modeling business processes Business summary certification changecontrol elicitation estimation futurethink information security innovationgames iterativedevelopment job job search kudos manage McDonalds persona productlines projectpurpose projectsuccess report requirements review roleplaying satire SCRUM SDLC shallstatements Survey teleseminar testplan tools use case usecase waterfall webcast writeArchives
- November 2011
- July 2011
- June 2011
- February 2011
- December 2010
- November 2010
- October 2010
- September 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- September 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- December 2008
- November 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
1 My Other Sites
2 Colleagues
3 BA Organizations
4 Interesting Blogs
Contact Us
Tag Archives: analyze
Tips for Business Analysts: Information – Kind of vs Form of
Author: Geri Schneider Winters When working on a project, you want to consider what kind of information you have, and what form is the best for documenting that information. These are two different things. A use case is a form … Continue reading
Tips for Business Analysts: What is Analysis?
Author: Geri Schneider Winters As Business Analysts, our job goes far beyond being a note-taker, in other words listening to people talk, writing down what they say and calling it requirements. Notice that the term Business Analyst implies that we … Continue reading
Tips for Business Analysts: Good Requirements
Author: Geri Schneider Winters Consider all the different kinds of requirements you write – Use Cases, Business Rules, Security, Database, Performance, Usability, Reliability, Regulatory, “shall” requirements. Good requirements are well-defined. How can you determine if your requirements are well defined? … Continue reading
