Project: Modern Analyst Knowledge Appraiser

Project Team

Perry McLeod - Team Lead & Lead BA

Adrian Marchis - Stakeholder


Live Project: Modern Analyst Knowledge Appraiser

The Modern Analyst Knowledge Appraiser is an initiative which has two main purposes:

  • Add a new feature to ModernAnalyst.com to allow community members to test (appraise) their business analysis and systems analysis skills.
  • To showcase a project "live" as it develops  so that members of the community who are more junior or just getting started can witness a project unfold and get a sense of the types of issues, challenges, and rewards that a business analyst or systems analyst experiences during the life of a project.

NOTE: All information, materials, content, and design of the Modern Analyst Knowledge Appraiser are copyright work of Modern Analyst Media LLC and are simply published as part of a sample project as a service to the business systems analysis community.

Project Diary: Knowledge Appraiser

Recent Entries | Categories | Search | Subscribe (RSS)

Stakeholder: Feedback to draft Requirements Work Plan

Hi Perry,

Here is my feedback (my comments are in bold and prefixed by AM): 
    1. In-Scope
  • HEY … IDEA ….. if this is good enough we can align to IIBA main site!!!!! Add to BC
    • AM: Can you elaborate on this?
  • Alignment with the Zachman Enterprise Architecture Framework
  • Alignment with the PMI® PMBOK® - second edition
  • Alignment with the IIBA® BABOK® - V1.6
  • An effective schema for each knowledge area's appraisal questions
    • AM: I see this project as having two distinct parts, the appraisal framework and the content.  The things that deal with PMBOK vs. BABOK vs. Zachman are content.  We should focus on both however we should clearly separate the two.  My vision is that this module is fully configurable so and will be maintained by an administrator via a UI.  So we should create the buiness entity model.  Here are some of the entities that I see will be there: Role, Competency, Knowledge Area, Question, User (to keep user profile), Keyword, Assesment Result (the result and dates of the test), etc.  Let's define these first.
  • Links to documents, essays, forms, blogs, or any other learning tool for each knowledge area
    • AM: I'm assuming these are resources for a given knowledge area that user can utilize to increase their skills.  Let's do this in the "future release" as oposed to v1. 
  • A personal assessment of the user's strengths and weakness for each knowledge area (topic suggestions are not limited to these suggestions alone)
    • Technical Appraisal – an assessment of the user's ability to understand general IT concepts and technologies
    • Project Lifecycles – an assessment of the user's ability to understand the major different types of project lifecycles (SDLC), their strengths and weaknesses (such as but not limited to object oriented analysis, structured analysis, business process modeling notation, rational unified process, base agile process principles, diagnostic modeling and joint application development)
    • Business Analysis – an assessment of the user's ability to understand the general concepts behind the profession of business analysis. What it is and what it is not.
    • Systems Analysis – an assessment of the user's ability to understand the general concepts behind the profession of systems analysis. In particular the delineation between business and systems analysis
    • Enterprise Architecture - an assessment of the user's ability to understand the planning framework of enterprise architecture and how it reflects on the overall analysis process
    • Requirements Planning and Management – an assessment of the user's ability to understand both product and project planning, how change is managed, how requirements are traced and tracked, how requirements are prioritized and allocated within the project lifecycle
    • Requirements Elicitation – an assessment of the user's ability to understand the process of effectively gathering stakeholder needs, approaches such as diagnostic modeling, verbal protocols, surveys, open and closed ended questioning and observation, object oriented and structured analysis approaches – then grouping those needs into regulatory, business (strategic, tactical, operational), user (functional, non-functional) and specification subject groups
    • Requirements Analysis – an assessment of the user's ability to understand the process of effectively analyzing the data gathered during elicitation, ability to define methods, tools and techniques and to structure the raw data into requirements (and gaps) that are visible, accountable, measurable and specific
    • Requirements Communication – an assessment of the user's ability to understand how to present and communicate requirements to all stakeholders and implementers of the project, to bring the group to consensus and approval, present the requirements in a format and structure that is appropriate such as a BRD or SRS
    • Requirements Assessment and Validation – an assessment of the user's ability to understand and develop alternate solutions, ensure quality, support the development and testing process, ensure buy-in and ensure traceability back to the stakeholder objectives
    • AM: Again, all these above ones are good but let's design the system/module to be flexible.  As you probably know already there is much debate in the BA community as to which is the exact list of roles, competencies, etc.  If we build a flexible tool we can simply change the data via and admin interface and we are ready to go.  This way this can also be used for assessing all kinds of sorts of things.
    1. Not-in-Scope
      1. AM: Let's call this "future release"/nice to have features
  • Comparative analysis between 2 appraisals from the same user taken at different times
  • Any type of percentile analysis of community's performance, as a whole
  • Any type of analytics of community's performance, as a whole
  • Group or team appraisals
  • A weighted scale between knowledge areas, as this will make any assessment calculations more difficult
  • Fks;ldgk;lasdkgskl;df

 

  • Assessment not to exceed 100 questions (10 KA's no more than 10 per KA)
    • AM: This should be another configurable option, this way we can modify this on the fly.  Imagine making this available to potential employers where they sign up for this service, put the candidate in a room and ask them to "take the test".  The employer could specify the # of questions per Role/KA/Competency and the KAs/Competencies they want to test.

    AM: Here are a couple of more requirements/vision details:

    At the high level, the Modern Analyst Appraiser allows a user to test their knowledge of analysis by answering a number of questions.

    -         User selects the domain areas that he/she wants to be tested in

    -         The system generates a list of questions

    -         The system displays a profile based on selected role

     
    The system shall allow the administrator to manage (CRUD) domain/KA/Competency areas, Roles, Questions, Keywords and associatons between Roles & Competencies/KAs, Competencies/KAs to Questions, Keywords to Questions.
     
    Have ability for Questions to be marked with a difficulty level ( i.e. easy, medium, hard).
     

    There should be an option would be for the analyst or employers to select one or more Roles (BA vs. SA) or one or more KA (Requirments Elicitation, etc.) or keywords (ex: UML, Activity Diagram, etc.) and the systems will ask the user a set of question based on the criteria.  A word on keywords: this is a great feature for the analyst to determine if they should put a given keyword on their resume or not.

     

    example:

     

    CREATE A MODERN ANALYST PROFILE

    Personal Profile

    Name: _________

    E-mail: _________

     

    Analysis Roles to Test

    þ Process Analyst

    þ Business Analyst

    þ Functional Architect

    þ Systems Analyst

    þ Designer/Architect

     

     

    Once the assesment is comple, I see the system generating a report something like this:

    MODERN ANALYST PROFILE

    Date:    October 8, 2006

    Name : James Underhill

    E-mail : [email protected]

     

    Best Fit: Business Analyst

     

    Competency Chart:

    ROLE

    RANKING

    PERCENTILE

    Process Analyst

    63%

    Business Analyst

    84%

    Functional Architect

    57%

    Systems Analyst

    30%

    Designer/Architect

    -

    8%

     

    Hope this provides you with more direction!

     

  • posted @ Tuesday, October 30, 2007 by adrian

    Previous Page | Next Page

    COMMENTS

    Only registered users may post comments.
    Registered Users Can...

     - view full diary entries,
    - download & view project files,
    - post comments.

    Login - Register

    Copyright 2006-2023 by Modern Analyst Media LLC