Action Research paper on Becoming an Artificial Intelligenc (AI) Analyst
Action Research Generic Proposal
The proposal section contains a high-level overview of your project as laid out in a minimum of
four iterations. Each iteration should represent approximately two weeks, with a minimum of
40 hours of activity in each iteration.
Do not try to layout your full plan at this point, keep this to one or two paragraphs for
each iteration description. At this point, you should focus on the big picture.
Hypothetical situation…Let’s say your proposal deals with improving the ‘needs
assessment’ process in organization XYZ. You know the process is weak and requires
improvement, but do not know what the weak points are or how to correct them. You
assume you will need the following iterations:
Iteration 1
In iteration 1, you anticipate two or three brainstorming sessions with representatives
from each of the three divisions with each session last a maximum of two hours. The
session discussions will include identifying current process flow, a gap analysis,
gathering process requirements, and communication flow. In addition, the iteration will
include compiling, analyzing, and reporting the results of each brainstorming session. At
this point you can go into a little more detail but not too much…keep this statement to
one or two paragraphs.
Remember, this is an example and one meeting is not sufficient for an iteration.
Iteration 2
You expect there will be several one-hour follow up session with each of the division
representatives to discuss the outcome of the brainstorming session, clarify information,
and gather more detail about their division’s requirements. Again keep this to one or two
paragraphs, I encourage you to focus on the big picture.
Remember, this is an example and one meeting is not sufficient for an iteration.
Iteration 3
This iteration will be a two-hour follow-up meeting with the three division
representatives to discuss identified common requirements, possible integration of
requirements, and discussion of how unique requirements will be managed at the division
level. The researcher will manage common and integrated requirements, and the
appropriate division must manage unique requirements. At the conclusion of this
meeting, the division representatives will be tasked with formulating a solution for all
unique requirements.
Remember, this is an example and one meeting is not sufficient for an iteration.
Iteration 4
You need to fully analyze the feedback concerning the requirements from each of the
divisions. Then, document a final process to collect ‘needs’ from each of the divisions,
Remember, this is an example and one meeting is not sufficient for an iteration.
Iteration 5
A final two-hour meeting is needed to present the new process. Copies of the new
process will be provided to each division.
Remember, this is an example and one meeting is not sufficient for an iteration.
A figure, see Figure 1, showing at least four iterations of your Action Research project’s
flow must appear at the end of your proposal. The figure shown here should be used as a
template for the information needed in the figure. Remember to revise the information in
each of the Iteration number blocks!
Iteration 1 Brainstorming &
Requ irements Gathering
Plan Act/
Actions Observation
/Results Reflection
Iteration 2 Divisional Meetings,
Data Analysis, & Other Research
Plan Act/
Actions Observation
/Results Reflection
Iteration 3 Coordination Meetings
& Data Analysis Plan
Act/ Actions
Observation /Results
Reflection
Iteration 4 Data Analysis & Do cumentation
Plan Act/
Actions Observation
/Results Reflection
Iteration 5 Project Finalization,
Repo rt Finalizatio n, & Fin dings Presen tation
Plan Act/
Actions Observation
/Results Reflection
Figure 1. Iteration flow diagram