{"id":2216,"date":"2019-03-26T22:43:05","date_gmt":"2019-03-27T03:43:05","guid":{"rendered":"https:\/\/rpchurchill.com\/wordpress\/?p=2216"},"modified":"2019-04-04T01:00:06","modified_gmt":"2019-04-04T06:00:06","slug":"combined-survey-results-late-march-2019","status":"publish","type":"post","link":"https:\/\/rpchurchill.com\/wordpress\/posts\/2019\/03\/26\/combined-survey-results-late-march-2019\/","title":{"rendered":"Combined Survey Results (late March 2019)"},"content":{"rendered":"<p>The additional survey results from <a href=\"https:\/\/rpchurchill.com\/wordpress\/posts\/2019\/03\/25\/a-simulationists-framework-for-business-analysis-round-five\/\">yesterday<\/a> are included in the combined results here.<\/p>\n<p><span style=\"text-decoration:underline\">List at least five steps you take during a typical business analysis effort.<\/span><\/p>\n<ol>\n<li>Requirements Gathering<\/li>\n<li>Initiation<\/li>\n<li>Testing<\/li>\n<li>QA<\/li>\n<li>Feedback<\/li>\n<li>User acceptance<\/li>\n<\/ol>\n<ol>\n<li>Requirement Elicitation<\/li>\n<li>UX Design<\/li>\n<li>Software Design for Testability<\/li>\n<\/ol>\n<ol>\n<li>Identify Business Goal<\/li>\n<li>ID Stakeholders<\/li>\n<li>Make sure necessary resources are available<\/li>\n<li>Create Project Schedule<\/li>\n<li>Conduct regular status meetings<\/li>\n<\/ol>\n<ol>\n<li>Meet with requester to learn needs\/wants<\/li>\n<li>List details\/wants\/needs<\/li>\n<li>Rough draft of Project\/proposed solutions<\/li>\n<li>Check in with requester on rough draft<\/li>\n<li>Make edits\/adjustments | test<\/li>\n<li>Regularly schedule touch-point meeting<\/li>\n<li>Requirement analysis\/design | functional\/non-functional<\/li>\n<li>Determine stakeholders | user acceptance<\/li>\n<\/ol>\n<ol>\n<li>List the stakeholders<\/li>\n<li>Read through all documents available<\/li>\n<li>Create list of questions<\/li>\n<li>Meet regularly with the stakeholders<\/li>\n<li>Meet with developers<\/li>\n<li>Develop scenarios<\/li>\n<li>Ensure stakeholders ensersy requirements<\/li>\n<li>other notes<\/li>\n<ul>\n<li>SMART PM milestones<\/li>\n<li>know players<\/li>\n<li>feedback<\/li>\n<li>analysis steps<\/li>\n<li>no standard<\/li>\n<\/ul>\n<\/ol>\n<ol>\n<li>identify stakeholders \/ Stakeholder Analysis<\/li>\n<li>identify business objectives \/ goals<\/li>\n<li>identify use cases<\/li>\n<li>specify requirements<\/li>\n<li>interview Stakeholders<\/li>\n<\/ol>\n<ol>\n<li>project planning<\/li>\n<li>user group sessions<\/li>\n<li>individual meetings<\/li>\n<li>define business objectives<\/li>\n<li>define project scope<\/li>\n<li>prototype \/ wireframes<\/li>\n<\/ol>\n<ol>\n<li>identify audience \/ stakeholders<\/li>\n<li>identify purpose and scope<\/li>\n<li>develop plan<\/li>\n<li>define problem<\/li>\n<li>identify objective<\/li>\n<li>analyze problems \/ identify alternative solutions<\/li>\n<li>determine solution to go with<\/li>\n<li>design solution<\/li>\n<li>test solution<\/li>\n<\/ol>\n<ol>\n<li>gathering requirements<\/li>\n<li>assess stakeholder priorities<\/li>\n<li>data pull<\/li>\n<li>data scrub<\/li>\n<li>data analysis<\/li>\n<li>create summary presentation<\/li>\n<\/ol>\n<ol>\n<li>define objective<\/li>\n<li>research available resources<\/li>\n<li>define a solution<\/li>\n<li>gather its requirements<\/li>\n<li>define requirements<\/li>\n<li>validate and verify requirements<\/li>\n<li>work with developers<\/li>\n<li>coordinate building the solutions<\/li>\n<\/ol>\n<ol>\n<li>requirements elicitation<\/li>\n<li>requirements analysis<\/li>\n<li>get consensus<\/li>\n<li>organizational architecture assessment<\/li>\n<li>plan BA activities<\/li>\n<li>assist UAT<\/li>\n<li>requirements management<\/li>\n<li>define problem to be solved<\/li>\n<\/ol>\n<ol>\n<li>understand thhe business need of the request<\/li>\n<li>understand why the need is important &#8211; what is the benefit\/value?<\/li>\n<li>identify the stakeholders affected by the request<\/li>\n<li>identify system and process impacts of the change (complexity of the change)<\/li>\n<li>understand the cost of the change<\/li>\n<li>prioritize the request in relation to other requests\/needs<\/li>\n<li>elicit business requirements<\/li>\n<li>obtain signoff on business requests \/ validate requests<\/li>\n<\/ol>\n<ol>\n<li>understanding requirements<\/li>\n<li>writing user stories<\/li>\n<li>participating in Scrums<\/li>\n<li>testing stories<\/li>\n<\/ol>\n<ol>\n<li>research<\/li>\n<li>requirements meetings\/elicitation<\/li>\n<li>document requirements<\/li>\n<li>requirements approvals<\/li>\n<li>estimation with developers<\/li>\n<li>consult with developers<\/li>\n<li>oversee UAT<\/li>\n<li>oversee business transition<\/li>\n<\/ol>\n<ol>\n<li>brainstorming<\/li>\n<li>interview project owner(s)<\/li>\n<li>understand current state<\/li>\n<li>understand need \/ desired state<\/li>\n<li>simulate \/ shadow<\/li>\n<li>inquire about effort required from technical team<\/li>\n<\/ol>\n<ol>\n<li>scope, issue determination, planning<\/li>\n<li>define issues<\/li>\n<li>define assumptions<\/li>\n<li>planning<\/li>\n<li>ccommunication<\/li>\n<li>analysis &#8211; business and data modeling<\/li>\n<\/ol>\n<ol>\n<li>gather data<\/li>\n<li>sort<\/li>\n<li>define<\/li>\n<li>organize<\/li>\n<li>examples, good and bad<\/li>\n<\/ol>\n<ol>\n<li>document analysis<\/li>\n<li>interviews<\/li>\n<li>workshops<\/li>\n<li>BRD walkthroughs<\/li>\n<li>item tracking<\/li>\n<\/ol>\n<ol>\n<li>ask questions<\/li>\n<li>gather data<\/li>\n<li>clean data<\/li>\n<li>run tests<\/li>\n<li>interpret results<\/li>\n<li>visualize results<\/li>\n<li>provide conclusions<\/li>\n<\/ol>\n<ol>\n<li>understand current state<\/li>\n<li>understand desired state<\/li>\n<li>gap analysis<\/li>\n<li>understand end user<\/li>\n<li>help customer update desired state\/vision<\/li>\n<li>deliver prioritized value iteratively<\/li>\n<\/ol>\n<ol>\n<li>define goals and objectives<\/li>\n<li>model As-Is<\/li>\n<li>identify gaps\/requirements<\/li>\n<li>model To-Be<\/li>\n<li>define business rules<\/li>\n<li>conduct impact analysis<\/li>\n<li>define scope<\/li>\n<li>identify solution \/ how<\/li>\n<\/ol>\n<ol>\n<li>interview project sponsor<\/li>\n<li>interview key stakeholders<\/li>\n<li>read relevant information about the issue<\/li>\n<li>form business plan<\/li>\n<li>communicate and get buy-in<\/li>\n<li>goals, objectives, and scope<\/li>\n<\/ol>\n<ol>\n<li>stakeholder analysis<\/li>\n<li>requirements gathering<\/li>\n<li>requirements analysis<\/li>\n<li>requirements management &#8211; storage and updates<\/li>\n<li>communication &#8211; requirements and meetings<\/li>\n<\/ol>\n<ol>\n<li>analyze evidence<\/li>\n<li>desiign application<\/li>\n<li>develop prototype<\/li>\n<li>implement product<\/li>\n<li>evaluate product<\/li>\n<li>train users<\/li>\n<li>upgrade functionality<\/li>\n<\/ol>\n<ol>\n<li>read material from previous similar projects<\/li>\n<li>talk to sponsors<\/li>\n<li>web search on topic<\/li>\n<li>play with current system<\/li>\n<li>ask questions<\/li>\n<li>draw BPMs<\/li>\n<li>write use cases<\/li>\n<\/ol>\n<ol>\n<li>document current process<\/li>\n<li>identify users<\/li>\n<li>meet with users; interview<\/li>\n<li>review current documentation<\/li>\n<li>present proposed solution or iteration<\/li>\n<\/ol>\n<ol>\n<li>meeting with stakeholders<\/li>\n<li>outline scope<\/li>\n<li>research<\/li>\n<li>write requirements<\/li>\n<li>meet and verify with developers<\/li>\n<li>test in development and production<\/li>\n<li>outreach and maintenance with stakeholders<\/li>\n<\/ol>\n<ol>\n<li>As-In analysis (current state)<\/li>\n<li>write lightweight business case<\/li>\n<li>negotiate with stakeholders<\/li>\n<li>write user stories<\/li>\n<li>User Acceptance Testing<\/li>\n<li>cry myself to sleep \ud83d\ude42<\/li>\n<\/ol>\n<ol>\n<li>initiation<\/li>\n<li>elicitation<\/li>\n<li>discussion<\/li>\n<li>design \/ user stories \/ use cases<\/li>\n<li>sign-off<\/li>\n<li>sprints<\/li>\n<li>testing \/ QA<\/li>\n<li>user acceptance testing<\/li>\n<\/ol>\n<ol>\n<li>planning<\/li>\n<li>elicitation<\/li>\n<li>requirements<\/li>\n<li>specification writing<\/li>\n<li>QA<\/li>\n<li>UAT<\/li>\n<\/ol>\n<ol>\n<li>identify the problem<\/li>\n<\/ol>\n<ol>\n<li>studying subject matter<\/li>\n<li>planning<\/li>\n<li>elicitation<\/li>\n<li>functional specification writing<\/li>\n<li>documentation<\/li>\n<\/ol>\n<ol>\n<li>identify stakeholders<\/li>\n<li>assess working approach (Waterfall, Agile, Hybrid)<\/li>\n<li>determine current state of requirements and maturity of project vision<\/li>\n<li>interview stakeholders<\/li>\n<li>write and validate requirements<\/li>\n<\/ol>\n<ol>\n<li>problem definition<\/li>\n<li>value definition<\/li>\n<li>decomposition<\/li>\n<li>dependency analysis<\/li>\n<li>solution assessment<\/li>\n<\/ol>\n<ol>\n<li>process mapping<\/li>\n<li>stakeholder interviews<\/li>\n<li>write use cases<\/li>\n<li>document requirements<\/li>\n<li>research<\/li>\n<\/ol>\n<ol>\n<li>listen &#8211; to stakeholders and customers<\/li>\n<li>analyze &#8211; documents, data, atc. to understand thhings further<\/li>\n<li>repeat back what I&#8217;m hearing to make sure I&#8217;m understanding correctly<\/li>\n<li>synthesize &#8211; the details<\/li>\n<li>document &#8211; as needed(e.g., Visio diagramsPowerPoint decks, Word, tool, etc.)<\/li>\n<li>solution<\/li>\n<li>help with implementing<\/li>\n<li>assess and improve &#8211; if\/as needed<\/li>\n<\/ol>\n<ol>\n<li>understand the problem<\/li>\n<li>understand the environment<\/li>\n<li>gather the requirements<\/li>\n<li>align with IT on design<\/li>\n<li>test<\/li>\n<li>train<\/li>\n<li>deploy<\/li>\n<li>follow-up<\/li>\n<\/ol>\n<ol>\n<li>watch how it is currently done<\/li>\n<li>listen to clients&#8217; pain points<\/li>\n<li>define goals of project<\/li>\n<\/ol>\n<ol>\n<li>critical path tasks<\/li>\n<li>pros\/cons of tasks<\/li>\n<li>impacts<\/li>\n<li>risks<\/li>\n<li>goals<\/li>\n<\/ol>\n<ol>\n<li>discovery &#8211; high level<\/li>\n<li>analysis \/ evaluation<\/li>\n<li>presentation of options<\/li>\n<li>requirements gathering<\/li>\n<li>epic \/ feature \/ story definition&#8217;<\/li>\n<li>prioritization<\/li>\n<\/ol>\n<ol>\n<li>who is driving the requirements?<\/li>\n<li>focus on what is needed for project<\/li>\n<li>who is going to use the product?<\/li>\n<\/ol>\n<ol>\n<li>elicit requirements<\/li>\n<li>hold focus groups<\/li>\n<li>create mock-ups<\/li>\n<li>test<\/li>\n<li>write user stories<\/li>\n<\/ol>\n<ol>\n<li>analyze<\/li>\n<li>document process<\/li>\n<li>identify waste (Lean)<\/li>\n<li>communicate<\/li>\n<li>document plan \/ changes<\/li>\n<\/ol>\n<ol>\n<li>meeting<\/li>\n<li>documentation<\/li>\n<li>strategy<\/li>\n<li>execution plan<\/li>\n<li>reporting plan<\/li>\n<\/ol>\n<ol>\n<li>requirements gathering<\/li>\n<li>delivery expectations<\/li>\n<li>user experience work with customer<\/li>\n<li>process mapping<\/li>\n<li>system and user testing<\/li>\n<li>system interaction (upstram and downstream) how does a change affect my process?<\/li>\n<li>understanding stakeholders<\/li>\n<\/ol>\n<ol>\n<li>stakeholder elicitation<\/li>\n<li>brainstorming<\/li>\n<li>requirements analysis<\/li>\n<li>wireframing<\/li>\n<li>process \/ flow diagrams<\/li>\n<\/ol>\n<ol>\n<li>current state analysis<\/li>\n<li>future state<\/li>\n<li>gap analysis<\/li>\n<li>requirements gathering<\/li>\n<li>success metrics<\/li>\n<\/ol>\n<ol>\n<li>interview users<\/li>\n<li>gather requirements<\/li>\n<li>document business rules<\/li>\n<li>business process flow<\/li>\n<li>mock-ups<\/li>\n<\/ol>\n<ol>\n<li>UX design review<\/li>\n<li>requirements gathering<\/li>\n<li>vision gathering \/ understanding<\/li>\n<\/ol>\n<ol>\n<li>requirements elicitation<\/li>\n<li>gap analysis<\/li>\n<\/ol>\n<ol>\n<li>shadow users<\/li>\n<li>follow up to verify understanding of business and need<\/li>\n<li>mockups, high-level design concept<\/li>\n<li>present mockup, design concept<\/li>\n<li>create and mintain stories and acceptance criteria<\/li>\n<\/ol>\n<ol>\n<li>brainstorming<\/li>\n<li>external stakeholder feedback<\/li>\n<li>internal stakeholder feedback<\/li>\n<li>break down epics<\/li>\n<li>user stories<\/li>\n<li>building<\/li>\n<\/ol>\n<ol>\n<li>stakeholder analysis<\/li>\n<li>elicitation activity plan<\/li>\n<li>requirements tracing<\/li>\n<li>prototyping<\/li>\n<li>document analysis<\/li>\n<\/ol>\n<ol>\n<li>research<\/li>\n<li>requirements analysis<\/li>\n<li>state chart diagram<\/li>\n<li>execution plan<\/li>\n<li>reporting plan<\/li>\n<\/ol>\n<p><span style=\"text-decoration:underline\">List some steps you took in a weird or non-standard project.<\/span><\/p>\n<ul>\n<li>Steps:<\/li>\n<ol>\n<li>1. Why is there a problem?  Is there a problem?<\/li>\n<li>2. What can change?  How can I change it?<\/li>\n<li>3. How to change the process for lasting results<\/li>\n<\/ol>\n<li>A description of &#8220;weird&#8221; usually goes along with a particular person I am working with rather than a project.  Some people like things done a certain way or they need things handed to them or their ego stroked.  I accommodate all kinds of idiosyncrasies so that I can get the project done on time.<\/li>\n<li>adjustments in project resources<\/li>\n<li>after initial interview, began prototyping and iterated through until agreed upon design<\/li>\n<li>built a filter<\/li>\n<li>create mock-ups and gather requirements<\/li>\n<li>create strategy to hit KPIs<\/li>\n<li>data migration<\/li>\n<li>data dictionary standardization<\/li>\n<li>describing resource needs to the customer so they better understand how much work actually needs to happen and that there isn&#8217;t enough staff<\/li>\n<li>design sprint<\/li>\n<li>design thinking<\/li>\n<li>developers and I create requirements as desired<\/li>\n<li>did my own user experience testing<\/li>\n<li>document requirements after development work has begun<\/li>\n<li>documented non-value steps in a process new to me<\/li>\n<li>explained project structure to stakeholders<\/li>\n<li>For a client who was unable to clearly explain their business processes and where several SMEs had to be consulted to form the whole picture, I drew workflows to identify inputs\/outputs, figure out where the gaps in our understanding existed, and identify the common paths and edge cases.<\/li>\n<li>got to step 6 (building) and started back at step 1 multiiple times<\/li>\n<li>guided solutioning<\/li>\n<li>identified handoffs between different contractors<\/li>\n<li>identify end results<\/li>\n<li>interview individuals rather than host meetings<\/li>\n<li>investigate vendor-provided code for business process flows<\/li>\n<li>iterative development and delivery<\/li>\n<li>made timeline promises to customers without stakeholder buy-in\/signoff<\/li>\n<li>make excutive decisions withoutstakeholder back-and-forth<\/li>\n<li>mapped a process flow on a meeting room wall and had developers stick up arrows and process boxes like I would create in Visio to get engagement and consensus<\/li>\n<li>moved heavy equipment<\/li>\n<li>moved servers from one office to another<\/li>\n<li>observe people doing un-automated process<\/li>\n<li>personally evaluate how comitted mgt was to what they said they wanted<\/li>\n<li>phased delivery \/ subject areas<\/li>\n<li>physically simulate each step of an operational process<\/li>\n<li>process development<\/li>\n<li>regular status reports to CEO<\/li>\n<li>resources and deliverables<\/li>\n<li>reverse code engineering<\/li>\n<li>review production incident logs<\/li>\n<li>showed customer a competitor&#8217;s website to get buy-in for change<\/li>\n<li>simulation<\/li>\n<li>start with techniques from junior team members<\/li>\n<li>starting a project without getting agreed funding from various units<\/li>\n<li>statistical modeling<\/li>\n<li>surveys<\/li>\n<li>team up with PM to develop a plan to steer the sponsor in the right diection<\/li>\n<li>town halls<\/li>\n<li>track progress in PowerPoint because the sponsor insisted on it<\/li>\n<li>train the team how to read use case diagrams<\/li>\n<li>translating training documents into Portuguese<\/li>\n<li>travel to affiliate sites to understand their processes<\/li>\n<li>understanding cultural and legal requirements in a foreign country<\/li>\n<li>use a game<\/li>\n<li>using a ruler to estimate level of effort to digitize paper contracts in filing cabinets gathered over 40 years<\/li>\n<li>work around manager who was afraid of change &#8211; had to continually demonstrate the product, ease of use, and savings<\/li>\n<li>worked with a mechanic<\/li>\n<li>write requirements for what had been developed<\/li>\n<\/ul>\n<p><span style=\"text-decoration:underline\">Name three software tools you use most.<\/span><\/p>\n<ul>\n<li>Excel (27)<\/li>\n<li>Visio (18)<\/li>\n<li>Jira (17)<\/li>\n<li>Word (15)<\/li>\n<li>Confluence (8)<\/li>\n<li>Outlook (7)<\/li>\n<li>PowerPoint (7)<\/li>\n<li>SharePoint (6)<\/li>\n<li>Azure DevOps (5)<\/li>\n<li>Google Docs (4)<\/li>\n<li>MS Team Foundation Server (4)<\/li>\n<li>email (3)<\/li>\n<li>MS Teams (3)<\/li>\n<li>Draw.io (2)<\/li>\n<li>MS Dynamics (2)<\/li>\n<li>MS Office (2)<\/li>\n<li>MS Visual Studio (2)<\/li>\n<li>Notepad (2)<\/li>\n<li>OneNote (2)<\/li>\n<li>Siebel (2)<\/li>\n<li>Slack (2)<\/li>\n<li>SQL Server (2)<\/li>\n<li>Version One (2)<\/li>\n<li>Adobe Reader (1)<\/li>\n<li>all MS products (1)<\/li>\n<li>ARC \/ Knowledge Center(?) (Client Internal Tests) (1)<\/li>\n<li>Balsamiq (1)<\/li>\n<li>Basecamp (1)<\/li>\n<li>Blueprint (1)<\/li>\n<li>Bullhorn (1)<\/li>\n<li>CRM (1)<\/li>\n<li>database, spreadsheet, or requirement tool for managing requirements (1)<\/li>\n<li>Doors (1)<\/li>\n<li>Enbevu(?) (Mainframe) (1)<\/li>\n<li>Enterprise Architect (1)<\/li>\n<li>Gephi (dependency graphing) (1)<\/li>\n<li>Google Calendar (1)<\/li>\n<li>Google Drawings (1)<\/li>\n<li>illustration \/ design program for diagrams (1)<\/li>\n<li>iRise (1)<\/li>\n<li>Kingsway Soft (1)<\/li>\n<li>Lucid Chart (1)<\/li>\n<li>LucidChart (1)<\/li>\n<li>Miro Real-Time Board (1)<\/li>\n<li>MS Office tools (1)<\/li>\n<li>MS Project (1)<\/li>\n<li>MS Word developer tools (1)<\/li>\n<li>NUnit (1)<\/li>\n<li>Pendo (1)<\/li>\n<li>Power BI (1)<\/li>\n<li>Process 98 (1)<\/li>\n<li>Python (1)<\/li>\n<li>R (1)<\/li>\n<li>requirements repositories, e.g., RRC, RTC  (1)<\/li>\n<li>RoboHelp (1)<\/li>\n<li>Scribe (1)<\/li>\n<li>Scrumhow (?) (1)<\/li>\n<li>Skype (1)<\/li>\n<li>SnagIt (1)<\/li>\n<li>SQL (1)<\/li>\n<li>Tableau (1)<\/li>\n<li>Visible Analyst (1)<\/li>\n<li>Visual Studio (1)<\/li>\n<li>Visual Studio Team Server (1)<\/li>\n<li>Vocera EVA (1)<\/li>\n<\/ul>\n<p><span style=\"text-decoration:underline\">Name three non-software techniques you use most.<\/span><\/p>\n<ul>\n<li>interviews (4)<\/li>\n<li>communication (3)<\/li>\n<li>brainstorming (2)<\/li>\n<li>meetings (2)<\/li>\n<li>process mapping (2)<\/li>\n<li>prototyping (2)<\/li>\n<li>relationship building (2)<\/li>\n<li>surveys (2)<\/li>\n<li>wireframing (2)<\/li>\n<li>&#8220;play package&#8221; (1)<\/li>\n<li>1-on-1 meetings to elicit requirements (1)<\/li>\n<li>active listening (1)<\/li>\n<li>analysis (1)<\/li>\n<li>analyze audience (1)<\/li>\n<li>apply knowledge of psychology to figure out how to approach the various personalities (1)<\/li>\n<li>business process analysis (1)<\/li>\n<li>business process modeling (1)<\/li>\n<li>calculator (1)<\/li>\n<li>change management (1)<\/li>\n<li>charting on whiteboard (1)<\/li>\n<li>coffees with customers (1)<\/li>\n<li>coffees with teams (1)<\/li>\n<li>collaboration (1)<\/li>\n<li>conference calls (1)<\/li>\n<li>conflict resolution and team building (1)<\/li>\n<li>costing out the requests (1)<\/li>\n<li>critical questioning (1)<\/li>\n<li>critical questioning (ask why fiive times), funnel questioning (1)<\/li>\n<li>data analysis (1)<\/li>\n<li>data modeling (1)<\/li>\n<li>decomposition (1)<\/li>\n<li>design thinking (1)<\/li>\n<li>develop scenarios (1)<\/li>\n<li>development efforts (1)<\/li>\n<li>diagramming\/modeling (1)<\/li>\n<li>document analysis (1)<\/li>\n<li>documentation (1)<\/li>\n<li>documenting notes\/decisions (1)<\/li>\n<li>drinking (1)<\/li>\n<li>elicitation (1)<\/li>\n<li>expectation level setting (1)<\/li>\n<li>face-to-face technique (1)<\/li>\n<li>facilitiation (1)<\/li>\n<li>fishbone diagram (1)<\/li>\n<li>Five Whys (1)<\/li>\n<li>focus groups (1)<\/li>\n<li>handwritten note-taking (1)<\/li>\n<li>hermeneutics \/ interpretation of text (1)<\/li>\n<li>impact analysis (1)<\/li>\n<li>individual meetings (1)<\/li>\n<li>informal planning poker (1)<\/li>\n<li>initial mockups  \/ sketches (1)<\/li>\n<li>interview (1)<\/li>\n<li>interview end user (1)<\/li>\n<li>interview stakeholders (1)<\/li>\n<li>interview users (1)<\/li>\n<li>interviewing (1)<\/li>\n<li>JAD sessions (Joint Application Development Sessions) (1)<\/li>\n<li>job shadowing (1)<\/li>\n<li>listening (1)<\/li>\n<li>lists (1)<\/li>\n<li>meeting facilitation (prepare an agenda, define goals, manage time wisely, ensure notes are taken and action items documented) (1)<\/li>\n<li>mind mapping (1)<\/li>\n<li>notes (1)<\/li>\n<li>note-taking (1)<\/li>\n<li>observation (1)<\/li>\n<li>organize (1)<\/li>\n<li>paper (1)<\/li>\n<li>paper easels (1)<\/li>\n<li>pen and paper (1)<\/li>\n<li>phone calls and fate-to-face meetings (1)<\/li>\n<li>Post-It notes (Any time of planning or breaking down of a subject, I use different colored Post-Its, writing with a Sharpie, on the wall.  This allows me to physically see an idea from any distance.  I can also move and categorize at will.  When done, take a picture.) (1)<\/li>\n<li>prioritization (MOSCOW) (1)<\/li>\n<li>process decomposition (1)<\/li>\n<li>process design (1)<\/li>\n<li>process flow diagrams (1)<\/li>\n<li>process modeling (1)<\/li>\n<li>product vision canvas (1)<\/li>\n<li>prototyping (can be on paper) (1)<\/li>\n<li>recognize what are objects (nouns) and actions (verbs) (1)<\/li>\n<li>requirements elicitation (1)<\/li>\n<li>requirements meetings (1)<\/li>\n<li>requirements verification and validation (1)<\/li>\n<li>requirements workshop (1)<\/li>\n<li>responsibility x collaboration using index cards (1)<\/li>\n<li>rewards (food, certificates) (1)<\/li>\n<li>Scrum Ceremonies (1)<\/li>\n<li>Scrums (1)<\/li>\n<li>shadowing (1)<\/li>\n<li>SIPOC (1)<\/li>\n<li>sketching (1)<\/li>\n<li>spreadsheets (1)<\/li>\n<li>stakeholder analysis (1)<\/li>\n<li>stakeholder engagement (1)<\/li>\n<li>stakeholder engagement &#8211; visioning to execution and post-assessment (1)<\/li>\n<li>stakeholder interviews (1)<\/li>\n<li>swim lanes (1)<\/li>\n<li>taking \/ getting feedback (1)<\/li>\n<li>taking notes (1)<\/li>\n<li>test application (1)<\/li>\n<li>training needs analysis (1)<\/li>\n<li>use paper models \/ process mapping (1)<\/li>\n<li>user group sessions (1)<\/li>\n<li>user stories (1)<\/li>\n<li>visual modeling (1)<\/li>\n<li>walking through client process (1)<\/li>\n<li>whiteboard diagrams (1)<\/li>\n<li>whiteboard workflows (1)<\/li>\n<li>whiteboarding (1)<\/li>\n<li>whiteboards (1)<\/li>\n<li>workflows (1)<\/li>\n<li>working out (1)<\/li>\n<li>workshops (1)<\/li>\n<\/ul>\n<p><span style=\"text-decoration:underline\">Name the goals of a couple of different projects (e.g., automate a manual process, interface to a new client, redesign screens, etc.)<\/span><\/p>\n<ul>\n<li>add enhancements to work flow app<\/li>\n<li>adding feature toggles for beta testing<\/li>\n<li>adhere to regulatory requirements<\/li>\n<li>adjusting solution to accommodate the needs of a new\/different user base<\/li>\n<li>automate a manual form with a workflow<\/li>\n<li>automate a manual login\/password generation and dissemination to users<\/li>\n<li>automate a manual process<\/li>\n<li>automate a manual process, reduce time and staff to accomplish a standard organizational function<\/li>\n<li>automate a paper-based contract digitization process<\/li>\n<li>automate and ease reporting (new tool)<\/li>\n<li>automate highly administrative, easily repeatable processes which have wide reach<\/li>\n<li>automate manual process<\/li>\n<li>automate new process<\/li>\n<li>automate risk and issue requirements<\/li>\n<li>automate the contract management process<\/li>\n<li>automate the process of return goods authorizations<\/li>\n<li>automate workflow<\/li>\n<li>automate workflows<\/li>\n<li>automation<\/li>\n<li>block or restore delivery service to areas affected by disasters<\/li>\n<li>bring foreign locations into a global system<\/li>\n<li>build out end user-owned applications into IT managed services<\/li>\n<li>business process architecture<\/li>\n<li>clear bottlenecks<\/li>\n<li>consolidate master data<\/li>\n<li>create a &#8220;how-to&#8221; manual for training condo board members<\/li>\n<li>create a means to store and manage condo documentation<\/li>\n<li>create a reporting mechanism for healthcare enrollments<\/li>\n<li>data change\/update<\/li>\n<li>data migration<\/li>\n<li>design processes<\/li>\n<li>develop a new process to audit projects in flight<\/li>\n<li>develop and interface between two systems<\/li>\n<li>develop data warehouse<\/li>\n<li>develop effort tracking process<\/li>\n<li>develop new functionality<\/li>\n<li>develop new software<\/li>\n<li>document current inquiry management process<\/li>\n<li>enhance current screens<\/li>\n<li>enhance system performance<\/li>\n<li>establish standards for DevOps<\/li>\n<li>establish vision for various automation<\/li>\n<li>I work for teams impplementing Dynamics CRM worldwide.  I specialize in data migration and integration.<\/li>\n<li>implement data interface wiith two systems<\/li>\n<li>implement new software solution<\/li>\n<li>implement software for a new client<\/li>\n<li>implement vendor software with customizations<\/li>\n<li>improve a business process<\/li>\n<li>improve system usability<\/li>\n<li>improve the usage of internal and external data<\/li>\n<li>improve user interface<\/li>\n<li>include new feature on mobile application<\/li>\n<li>increase revenue and market share<\/li>\n<li>integrate a new application with current systems\/vendors<\/li>\n<li>maintain the MD Product Evaluation List (online)<\/li>\n<li>map geographical data<\/li>\n<li>merge multiple applications<\/li>\n<li>migrate to a new system<\/li>\n<li>move manual Excel reports online<\/li>\n<li>new functionality<\/li>\n<li>process data faster<\/li>\n<li>process HR data and store records<\/li>\n<li>product for new customer<\/li>\n<li>prototype mobile app for BI and requirements<\/li>\n<li>provide business recommendations<\/li>\n<li>provide new functionality<\/li>\n<li>recover fuel-related cost fluctuations<\/li>\n<li>redesign<\/li>\n<li>redesign a system process to match current business needs<\/li>\n<li>reduce technical debt<\/li>\n<li>re-engineer per actual user requirements<\/li>\n<li>reimplement solution using newer technology<\/li>\n<li>replace current analysis tool with new one<\/li>\n<li>replace legacy system<\/li>\n<li>replace manual tools with applications<\/li>\n<li>replatform legacy system<\/li>\n<li>rewrite \/ redesign screens<\/li>\n<li>simplify \/ redesign process<\/li>\n<li>simplify returns for retailer and customer<\/li>\n<li>standardize \/ simplify a process or interface<\/li>\n<li>system integration<\/li>\n<li>system integration \/ database syncing<\/li>\n<li>system performance improvements<\/li>\n<li>system-to-system integration<\/li>\n<li>technical strategy for product<\/li>\n<li>transform the customer experience (inside and outside)<\/li>\n<li>UI optimization<\/li>\n<li>update a feature on mobile app<\/li>\n<li>update the e-commerce portion of a website to accept credit and debit cards<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The additional survey results from yesterday are included in the combined results here. List at least five steps you take during a typical business analysis effort. Requirements Gathering Initiation Testing QA Feedback User acceptance Requirement Elicitation UX Design Software Design &hellip; <a href=\"https:\/\/rpchurchill.com\/wordpress\/posts\/2019\/03\/26\/combined-survey-results-late-march-2019\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[226,192,191,186,193,142],"_links":{"self":[{"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/posts\/2216"}],"collection":[{"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/comments?post=2216"}],"version-history":[{"count":5,"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/posts\/2216\/revisions"}],"predecessor-version":[{"id":2221,"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/posts\/2216\/revisions\/2221"}],"wp:attachment":[{"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/media?parent=2216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/categories?post=2216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rpchurchill.com\/wordpress\/wp-json\/wp\/v2\/tags?post=2216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}