I was finally able to give this talk to the IIBA’s Baltimore Chapter. The results of the newest survey are below, and the results from the initial talks are here and here. The link to the current version of the presentation follows directly.
https://www.rpchurchill.com/presentations/SimFrameForBA/index.html
Here are the latest survey results.
List at least five steps you take during a typical business analysis effort.
- stakeholder analysis
- requirements gathering
- requirements analysis
- requirements management – storage and updates
- communication – requirements and meetings
- analyze evidence
- design application
- develop prototype
- implement product
- evaluate product
- train users
- upgrade functionality
- read material from previous similar projects
- talk to sponsors
- web search on topic
- play with current system
- ask questions
- draw BPMs
- write use cases
- document current process
- identify users
- meet with users; interview
- review current documentation
- present proposed solution or iteration
- meeting with stakeholders
- outline scope
- research
- write requirements
- meet and verify with developers
- test in development and production
- outreach and maintenance with stakeholders
- As-Is analysis (current state)
- write lightweight business case
- negotiate with stakeholders
- write user stories
- User Acceptance Testing
- cry myself to sleep đŸ™‚
- initiation
- elicitation
- discussion
- design / user stories / use cases
- sign-off
- sprints
- testing / QA
- user acceptance testing
List some steps you took in a weird or non-standard project.
- documented non-value steps in a process new to me
- guided solutioning
- identified handoffs between different contractors
- iterative development and delivery
- make executive decisions without stakeholder back-and-forth
- personally evaluate how committed management was to what they said they wanted
- phased delivery / subject areas
- starting a project without getting agreed funding from various units
- work around manager who was afraid of change – had to continually demonstrate the product, ease of use, and savings
Name three software tools you use most.
- Excel (4)
- Jira (3)
- Word (3)
- Confluence (2)
- PowerPoint (2)
- e-mail (1)
- Google Docs (1)
- Google Drawings (1)
- MS Word developer tools (1)
- RoboHelp (1)
- SharePoint (1)
- SnagIt (1)
- Visio (1)
Name three non-software techniques you use most.
- analysis
- analyze audience
- apply knowledge of psychology to figure out how to approach the various personalities
- communication
- expectation level setting
- JAD sessions (Joint Application Development Sessions)
- meetings
- phone calls and fate-to-face meetings
- “play package”
- process flow diagrams
- prototyping
- test application
- training needs analysis
- user stories
- whiteboard diagrams
- wireframing
- workflows
Name the goals of a couple of different projects (e.g., automate a manual process, interface to a new client, redesign screens, etc.)
- automate and ease reporting (new tool)
- automate the contract management process
- automation
- block or restore delivery service to areas affected by disasters
- create a “how-to” manual for training condo board members
- create a means to store and manage condo documentation
- create a reporting mechanism for healthcare enrollments
- develop data warehouse
- develop effort tracking process
- develop new functionality
- document current inquiry management process
- maintain the MD Product Evaluation List (online)
- move manual Excel reports online
- process HR data and store records
- recover fuel-related cost fluctuations
- redesign
- reduce technical debt
- re-engineer per actual user requirements
- replace current analysis tool with new one
- simplify returns for retailer and customer
A compilation of results from all three surveys will be posted shortly.