{"id":2173,"date":"2019-02-28T21:09:54","date_gmt":"2019-03-01T02:09:54","guid":{"rendered":"https:\/\/rpchurchill.com\/wordpress\/?p=2173"},"modified":"2019-03-17T22:47:40","modified_gmt":"2019-03-18T03:47:40","slug":"business-analysis-survey-round-five","status":"publish","type":"post","link":"https:\/\/rpchurchill.com\/wordpress\/posts\/2019\/02\/28\/business-analysis-survey-round-five\/","title":{"rendered":"Business Analysis Survey: Round Five"},"content":{"rendered":"

I collected more survey responses at the recent Tampa IIBA meetup<\/a>, and the results are posted below.<\/p>\n

List 5-8 steps you take during a typical project.<\/span><\/p>\n

    \n
  1. listen – to stakeholders and customers<\/li>\n
  2. analyze – documents, data, atc. to understand thhings further<\/li>\n
  3. repeat back what I’m hearing to make sure I’m understanding correctly<\/li>\n
  4. synthesize – the details<\/li>\n
  5. document – as needed(e.g., Visio diagramsPowerPoint decks, Word, tool, etc.)<\/li>\n
  6. solution<\/li>\n
  7. help with implementing<\/li>\n
  8. assess and improve – if\/as needed<\/li>\n<\/ol>\n
      \n
    1. understand the problem<\/li>\n
    2. understand the environment<\/li>\n
    3. gather the requirements<\/li>\n
    4. align with IT on design<\/li>\n
    5. test<\/li>\n
    6. train<\/li>\n
    7. deploy<\/li>\n
    8. follow-up<\/li>\n<\/ol>\n
        \n
      1. watch how it is currently done<\/li>\n
      2. listen to clients’ pain points<\/li>\n
      3. define goals of project<\/li>\n<\/ol>\n
          \n
        1. critical path tasks<\/li>\n
        2. pros\/cons of tasks<\/li>\n
        3. impacts<\/li>\n
        4. risks<\/li>\n
        5. goals<\/li>\n<\/ol>\n
            \n
          1. discovery – high level<\/li>\n
          2. analysis \/ evaluation<\/li>\n
          3. presentation of options<\/li>\n
          4. requirements gathering<\/li>\n
          5. epic \/ feature \/ story definition’<\/li>\n
          6. prioritization<\/li>\n<\/ol>\n
              \n
            1. who is driving the requirements?<\/li>\n
            2. focus on what is needed for project<\/li>\n
            3. who is going to use the product?<\/li>\n<\/ol>\n
                \n
              1. elicit requirements<\/li>\n
              2. hold focus groups<\/li>\n
              3. create mock-ups<\/li>\n
              4. test<\/li>\n
              5. write user stories<\/li>\n<\/ol>\n
                  \n
                1. analyze<\/li>\n
                2. document process<\/li>\n
                3. identify waste (Lean)<\/li>\n
                4. communicate<\/li>\n
                5. document plan \/ changes<\/li>\n<\/ol>\n
                    \n
                  1. meeting<\/li>\n
                  2. documentation<\/li>\n
                  3. strategy<\/li>\n
                  4. execution plan<\/li>\n
                  5. reporting plan<\/li>\n<\/ol>\n

                    List some steps you took on a weird or non-standard project.<\/span><\/p>\n