Bibliography

Ambler, Scott (2005). The Elements of UML 2.0 Style. Cambridge University Press.

Bittner, Kurt and Ian Spence (2002). Use Case Modeling. Addison-Wesley.

Chen, Peter Pin-Shan (1976). The entity-relationship model—Toward a unified view of data. ACM Transaction on Database Systems. Vol. 1, No. 1 (March).

Cockburn, Alister (2000). Writing Effective Use Cases. Addison-Wesley Professional.

Cohn, Mike (2004). User Stories Applied: For Agile Software Development. Addison-Wesley Professional.

Gottensdiener, Ellen (2005). The Software Requirements Memory Jogger. GOAL/QPC.

Jacobson, Ivar (1992). Object Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley Professional.

Lauesen, Soren (2002). Software Requirements: Styles and Techniques. Addison-Wesley.

Martin, James (1986). Information Engineering. Savant.

Martin, James and C. McClure (1985). Diagramming Techniques for Analysts and Programmers. Prentice Hall.

Page-Jones, Meilir (1988). The Practical Guide to Structured Systems Design. Second Edition. Prentice Hall PTR.

Pande, Peter S., Robert P. Neuman, and Roland R. Cavanagh (2000). The Six Sigma Way: How GE, Motorola, and Other Top Companies Are Honing Their Performance. McGraw-Hill.

Ross, Ronald (2003). Principles of the Business Rule Approach. Addison-Wesley.

Simsion, Grame C. and Graham C. Witt (2005). Data Modeling Essentials. Second Edition. Morgan Kaufman.

van Duyne, Douglas K., James A. Landay, and Jason I. Hong (2006). The Design of Sites: Patterns for Creating Winning Web Sites. Second Edition. Prentice Hall PTR.

von Halle, Barbara (2003). Business Rules Applied: Building Better Systems Using the Business Rules Approach. John Wiley & Sons.

Wiegers, Karl (1999). Software Requirements. Microsoft Press.

Yourdon, Edward (1988). Modern Structured Analysis. Prentice Hall PTR.

Yourdon, Edward and Larry Constantine (1979). Structured Design: Fundamentals of a Discipline of Computer Program and System Design. Prentice Hall.

Chapter 7: Increase Your Value overview

One of the great things about business analysis is that you can increase your value to an organization by learning new techniques and continuously improving your skills. A business analyst (BA) initially learns the foundational skills of communications and requirements techniques and then builds on that foundation, maturing as he or she gains more and more experience. A business analysis professional has unlimited possibilities for career development and expanding responsibilities. The skills used in business analysis work are prized by organizations and offer BAs the opportunity to move into management and executive positions if interested.

Many of the skills used in business analysis work are also used in related disciplines. Project management, quality assurance, business management, and strategic planning professionals all share skills with business analysis that are never really perfected, but rather enhanced.

There are numerous ways to improve your skills: read books and articles, practice new techniques and skills, and learn from other BAs. You also improve your skills when you teach other people. Join a business analysis community like your local International Institute of Business Analysis (IIBA™) chapter or your company’s business analysis community of practice, help the group schedule meetings and find speakers to improve your leadership skills, volunteer to mentor new BAs, and give presentations to share your knowledge. Join other industry groups focused on IT, process improvement, or your industry. Sharing your experiences helps other BAs and improves the professional as a whole.

The skills and techniques presented in this chapter are not learned in any particular order. They are grouped into the following general sections:

• Build Your Foundation

• Time Management

• Build Your Relationships and Communication Skills

• Keep Learning New Analysis Techniques

• Continually Improve Your Skills

• Business Analysis Planning