| Category | OTHM Level 7 Assignment | Subject | Management |
|---|---|---|---|
| University | Module Title | J/618/5990 Project Development, Planning and Management |
In this module, some basics of research projects, particularly from a DBA point of view, will be introduced. It identifies different problems and constraints in research that researchers encounter in a typical DBA programme, and it is intended to educate the participants about good practices in DBA research management.
Be sure to use this sample for learning purposes only. The material listed above may be vulnerable if copied from this sample. All assignments will undergo plagiarism checking, and any assignment will be plagiarism-checked by plagiarism detection software. Plagiarism will cause the assignment or tasks to fail if it is discovered in the file.
Need Help With the Complete J/618/5990 Project Development, Planning and Management Assignment? Get Expert Assignment Solutions Before Your Deadline
Get Complete Unit Assignment SupportProjects are now the primary means of organisations to bring about change, innovation and strategic value. However, they are complex, uncertain and interdependent and are difficult to manage, with evidence of cost overruns, delays and benefit shortfalls. Many of these qualities are suitable to a DBA research project. It has clear outcomes, has a definite end date, has limited resources and numerous stakeholders. Unlike an organisational project, it does not have an organisational output but rather a new body of knowledge, and it is evaluated both for scholarly rigour as well as practical relevance. This proposal thus serves two purposes: to establish the validity of the research problem and to demonstrate the project planning, resourcing and management process through the application of the recognised project management principles.
The research will explore the implementation of Generative Artificial Intelligence (AI) by small and medium-sized enterprises (SMEs) in operational decision-making. The use of AI is widely heralded as a productivity and competitive advantage. SMEs, however, are generally small in size and lack the required capital, specialist skills and formal governance structures, which make them less likely than other organisations to be involved in formal adoption programs, but more likely to be involved in informal adoption programs. This is a practical question: Companies can spend time and money but may not have a way to plan, sequence and measure the impact of adoption.
Projects are now the primary means of organisations to bring about change, innovation and strategic value. However, they are complex, uncertain and interdependent and are difficult to manage, with evidence of cost overruns, delays and benefit shortfalls. Many of these qualities are suitable to a DBA research project. It has clear outcomes, has a definite end date, has limited resources and numerous stakeholders. Unlike an organisational project, it does not have an organisational output but rather a new body of knowledge, and it is evaluated both for scholarly rigour as well as practical relevance. This proposal thus serves two purposes: to establish the validity of the research problem and to demonstrate the project planning, resourcing and management process through the application of the recognised project management principles.
The research will explore the implementation of Generative Artificial Intelligence (AI) by small and medium-sized enterprises (SMEs) in operational decision-making. The use of AI is widely heralded as a productivity and competitive advantage. SMEs, however, are generally small in size and lack the required capital, specialist skills and formal governance structures, which make them less likely than other organisations to be involved in formal adoption programs, but more likely to be involved in informal adoption programs. This is a practical question: Companies can spend time and money but may not have a way to plan, sequence and measure the impact of adoption.
There are three arguments for the rationale.
Practical. While SMEs play a crucial role in driving the economy, the guidance available on how to use AI is predominantly geared towards organisations that have dedicated technology teams. The approach that managers require must be realistic for resource-constrained firms.
Theoretical. Existing models of adoption were developed before the emergence of generative AI and concentrate primarily on adoption factors or individual adoption intention, including the Technology-Organisation-Environment framework and the Unified Theory of Acceptance and Use of Technology. They do not say much about how adoption is treated as a project throughout its lifecycle. This gap is discussed further in the literature discussion.
Personal and professional. The DBA is appropriate because it will involve professional practice and academic research.
The aims of the project are:
validated and practice-oriented framework for managing AI adoption in SMEs, contribution to AI adoption and project management theory, peer-reviewed publication(s), development of my competence in planning and managing complex and long-term research.
Research Goal, Aims and Objectives
Aim: Design and test a project-based approach which enables SMEs to plan and manage the use of generative AI in operational decision-making.
Objectives (assuming a 36-month part-time DBA):
Practical. While SMEs play a crucial role in driving the economy, the guidance available on how to use AI is predominantly geared towards organisations that have dedicated technology teams. The approach that managers require must be realistic for resource-constrained firms.
Theoretical. Existing models of adoption were developed before the emergence of generative AI and concentrate primarily on adoption factors or individual adoption intention, including the Technology-Organisation-Environment framework and the Unified Theory of Acceptance and Use of Technology. They do not say much about how adoption is treated as a project throughout its lifecycle. This gap is discussed further in the literature discussion.
Personal and professional. The DBA is appropriate because it will involve professional practice and academic research.
validated and practice-oriented framework for managing AI adoption in SMEs, contribution to AI adoption and project management theory, peer-reviewed publication(s), development of my competence in planning and managing complex and long-term research.
Research Goal, Aims and Objectives
Aim: Design and test a project-based approach which enables SMEs to plan and manage the use of generative AI in operational decision-making.
Objectives (assuming a 36-month part-time DBA):
| S.No. | Objective | Specific, measurable outcome | Deadline |
|
O1 |
Critically analyse the literature relating to the adoption of technology and project management in SMEs. |
Create a synthesis matrix using 60 or more peer-reviewed sources. |
Month 6 |
|
O2 |
Develop a research design and obtain approval for research ethics. |
Research design and ethics clearance approved |
Month 9 |
|
O3 |
Gather first-hand information from SME practitioners. |
Interviews and surveys with at least 150 managers and 15 semi-structured interviews. |
Month 21 |
|
O4 |
Examine data to find out what is most likely to enable and constrain adoption. |
The codebook and validated factor structure are available. |
Month 27 |
|
O5 |
Develop and validate the framework |
A panel of 8-10 practitioners reviewed the Framework. |
Month 32 |
|
O6 |
Complete and disseminate the research |
Thesis submitted and one journal article under review |
Month 36 |
SMART justification. Each objective has a specific deliverable, and there is a measurable outcome that is a numerical or documentary output. They are attainable due to the small sample sizes and the availability of access to SME managers. These are relevant as they each contribute directly to the aim. They have a set month and can track milestones in the project plan.
Scope. The study concentrates only on companies with 10-249 employees. It's about generative AI for operational decisions, not AI for product development or customer-facing. The boundaries are established to ensure that the project is manageable in terms of time (36 months) and resources (one researcher).
Past studies and the need for further research are discussed.
Technology adoption theory. Early work accounts for adoption in terms of the perspective of individuals. Davis (1989) demonstrated that perceived usefulness and ease of use are factors that influence technology acceptance, and Venkatesh et al. (2003) merged eight models into the UTAUT, extending it to the consumer context by Venkatesh et al. (2012). Rogers (2003) explained the process of innovation diffusion at the social system level, and Tornatzky and Fleischer (1990) introduced the idea that technological, organisational and environmental factors influence adoption. These models are useful and proven. They are limited in that they see adoption as something that is to be decided upon or intended, not something to be managed. They are also more predated by the accessibility, probabilistic outputs and quick evolution of generative AI, which formed the basis of enterprise systems.
The implementation of AI in businesses. The studies of AI in business have been picking up the pace. Ransbotham et al. (2017) discovered that while many companies play around with AI, few reap meaningful rewards, indicating that the problem is not that companies don't have access to the technology, but that many companies are not capable of implementing it. The impact of AI on the organisation's functioning and decision-making calls for new organisational structures, as proposed by Iansiti and Lakhani (2020). Dwivedi et al. (2023) provide a cross-disciplinary perspective on generative AI with regard to opportunities, risks and research agendas and propose empirical research on the use of generative AI in organisations. One weakness in this body of literature is that it solely addresses large companies with data science departments, and many are conceptual or consultancy-generated and not empirical.
SMEs and Technology adoption. What is generally agreed across studies of SMEs is limited financial resources, skills shortages, and the dominance of owner-managers as factors shaping adoption, and that these factors are mostly applied to the adoption of previous technologies, including e-commerce and enterprise systems. There is some evidence of the use of generative AI in SMEs, but it is limited. Most studies rely on country-based cross-sectional surveys and quantify intention to adopt, not the adoption process. Include 2-3 recent (2023-2025) SME specific generative AI studies and summarise the samples, methods and limitations.
Project management and Successful implementation. There is separate literature available about the success and failure of initiatives. Pinto and Slevin (1987) determined critical success factors to be top management support, clear objectives and monitoring, and Cooper (1990) demonstrated that stage-gate processes structure innovation by mitigating uncertainty at key decision points. Shenhar and Dvir (2007) state that it is important to tailor project approaches to novelty, technology, and pace. This work is seldom related to technology adoption studies, and very little of it focuses on small firms, which usually lack project offices and formal governance.
Gap and justification. Combining all the literature reveals four limitations:
There is no standardised approach that combines these streams for resource-poor SMEs leveraging generative AI. It is this gap that the project aims to fill, and the project goal of creating a project-based framework (Section 2) justifies it. It also facilitates a mixed-methods approach: surveys can help uncover trends in enablers and barriers across numerous firms, and interviews can help to reveal how adoption is handled in practice.
4. Data Requirements
Data should be required by the project objectives. Requirements are prioritised using MoSCoW prioritisation (Clegg and Barker, 1994), and this also assists in maintaining scope should time and/or access be limited, for example.
|
Priority |
Data requirement |
Source |
Linked objective |
|
Must have |
Adoption status, enablers, barriers and management practices. |
SME managers were contacted through a questionnaire that was distributed online. |
O3, O4 |
|
Must have |
Semi-structured interview data relating to the planning, resourcing and evaluation of adoption (15 interviews) |
The owner-managers of SMEs and technology leads. |
O3, O4 |
|
Must have |
Peer-reviewed literature (60+ sources) |
Academic databases |
O1 |
|
Should have |
Feedback from experts on the draft framework (8-10 practitioners) |
Academics, adoption leads, consultation |
O5 |
|
Should have |
Firm characteristics (size, sector, digital maturity) as control variables. |
Survey demographics |
O4 |
|
Could have |
Documentary evidence including adoption plans, budgets/policies |
Participating firms |
O4 |
|
Could have |
Secondary data are statistics on the rates of adoption of AI for SMEs. |
The government and industry reports are also available. |
O1 |
|
Won’t have (this time) |
Adoption studies focus on tracking firms' performance over time. |
Not covered for the next 36 months. |
n/a |
There is no standardised approach that combines these streams for resource-poor SMEs leveraging generative AI. It is this gap that the project aims to fill, and the project goal of creating a project-based framework (Section 2) justifies it. It also facilitates a mixed-methods approach: surveys can help uncover trends in enablers and barriers across numerous firms, and interviews can help to reveal how adoption is handled in practice.
4. Data Requirements
Data should be required by the project objectives. Requirements are prioritised using MoSCoW prioritisation (Clegg and Barker, 1994), and this also assists in maintaining scope should time and/or access be limited, for example.
Data types and quality. The survey is used to collect quantitative data that is appropriate for descriptive and multivariate analysis, while the interviews are used to collect qualitative data appropriate to thematic analysis (Braun and Clarke, 2006). Their use is based on a mixed-methods design (Creswell and Plano Clark, 2018). Primary data introduces ethical issues, which are covered under O2: informed consent, anonymity, secure storage and GDPR compliance.
Access risk. The major data relies on the managers of SMEs agreeing to participate. This is the top risk in the project and will be incorporated into the risk management plan, with actions like hiring early via [your professional connections] and conducting a pilot survey.
Potential Contribution to knowledge and Novelty
Theoretical contribution. Current technology adoption models provide a description of whether or not a technology is adopted and not how it is planned, sequenced and controlled. This project builds on the adoption theory as an extension of its concept of adoption being a project that has a life cycle: initiation, planning, execution, monitoring and closure. It links two streams of research that grew more or less independently – technology adoption and project management. It also investigates whether models developed for previous enterprise technologies are applicable in the context of generative AI, which is easily accessible, straightforward to use, and unreliable in terms of results. Last, it provides empirical evidence from small companies, where formal governance and project offices and specialist roles are typically not found.
Practical contribution. The primary result is a framework which the managers of SMEs can work with without having an entire technology team. As originally designed, it contains:
Secondary beneficiaries are SME support bodies who may be able to leverage the results for training and advisory programmes, and consultants to small firms. The framework is based on practitioner evidence and is tested through an expert panel, meaning that it is intended to be usable and not a purely conceptual framework.
Novelty. The project is new in four aspects:
Limitations and transferability. The study is limited to the sector and region, and findings might need to be adapted elsewhere. The framework was designed as a starting point for further studies in different contexts and/or over time.
Assistance to the researcher. The project is also an example of the integration of professional practice and scholarly inquiry for the DBA. It develops the researcher's ability in research design, project control and dissemination.
A mixed approach is being used in the project. The research phases of the stage-gate structure align well with the research, which has distinct phases and decision points: (literature, design, collection, analysis, framework, thesis). Short cycles of testing/improving activities within each phase can enable revision if evidence shifts.
The plan is managed using:
Funding and resourcing issues (illustrative). The project is expected to have some funding from the employer and be self-funded. Funding sources include institutional bursaries, small bursaries from professional societies and employer sponsorship. The plan is designed to be independent of grant revenue.
| WP | Work package | Months | Linked objective | Key output |
| WP1 |
Scoping and literature review |
1-6 |
O1 |
Synthesis matrix (60+ sources) |
| WP2 |
Methodology and ethics |
3-9 |
O2 |
Approved design and ethics clearance |
| WP3 |
Instrument development and pilot |
10-12 |
O3 |
Validated survey and interview guide |
| WP4 |
Data collection |
13-20 |
O3 |
150+ survey responses; 15 interviews |
| WP5 |
Data analysis |
19-27 |
O4 |
Coded dataset; factor model |
| WP6 |
Framework development and validation |
28-32 |
O5 |
Validated framework |
| WP7 |
Thesis writing and dissemination |
10-36 |
O6 |
Thesis and one journal article |
| WP8 |
Project management and supervision |
1-36 |
All |
Progress reports, risk log |
| ID | Activity | Duration (months) | Predecessor | Float |
| A1 |
Scoping and topic confirmation |
2 |
None |
0 |
| A2 |
Literature search and synthesis |
4 |
A1 |
High* |
| A3 |
Methodology design |
4 |
A1 |
0 |
| A4 |
Ethics application and approval |
3 |
A3 |
0 |
| A5 |
Instrument development and pilot |
3 |
A4 |
0 |
| A6 |
Survey data collection |
6 |
A5 |
4 |
| A7 |
Interview data collection |
8 |
A5 |
0 |
| A8 |
Quantitative analysis |
4 |
A6 |
4 |
| A9 |
Qualitative analysis |
6 |
A7 |
0 |
| A10 |
Mixed-methods integration |
1 |
A8, A9 |
0 |
| A11 |
Framework design |
3 |
A10 |
0 |
| A12 |
Expert panel validation |
2 |
A11 |
0 |
| A13 |
Draft early thesis chapters |
4 |
A4 |
High* |
| A14 |
Complete and submit thesis |
4 |
A12, A13 |
0 |
| A15 |
Journal article preparation |
3 |
A12 |
1 |
Large network float for A2 and A13, but A2 is held up to month 6 to spread up the writing load and A13 is writing early to ensure the continuity of the writing load.
6.4 Critical path
The critical path is the longest path of activities through the project that have no slack time, or float:
A1 → A3 → A4 → A5 → A7 → A9 → A10 → A11 → A12 → A14
Durations: 2 + 4 + 3 + 3 + 8 + 6 + 1 + 3 + 2 + 4 = 36 months, matching the programme length. These activities will be delayed by the same period of time if they are delayed.
This implies two things:
6.5 Milestones
|
Milestone |
Month |
Gate criterion |
|
M1: Literature review complete |
6 |
O1 met; supervisor sign-off |
|
M2: Ethics approval received |
9 |
O2 met; no data collected before this |
|
M3: Pilot complete, instruments finalised |
12 |
Pilot feedback incorporated |
|
M4: Data collection complete |
21 |
O3 targets reached (or agreed fallback) |
|
M5: Analysis complete |
27 |
O4 met |
|
M6: Framework validated |
32 |
O5 met; expert panel feedback logged |
|
M7: Thesis submitted |
36 |
O6 met |
6.6 Resource optimisation
The resources are limited primarily by the time of the researcher, which is about 12 hours per week or approximately 1800 hours total. There are four steps to ensure the use is efficient:
6.7 Estimated cost (illustrative, GBP)
|
Item |
Cost (£) |
|
Survey platform licence |
600 |
|
Participant recruitment and incentives |
1,500 |
|
Interview transcription (15 interviews) |
1,500 |
|
Qualitative analysis software |
700 |
|
Statistical software and data storage |
700 |
|
Conference travel and registration |
2,500 |
|
Expert panel honoraria |
500 |
|
Proofreading and open-access fees |
1,200 |
|
Subtotal |
9,200 |
|
Contingency (10%) |
920 |
|
Total |
10,120 |
This budget does not include tuition fees. The effort estimate above includes the time cost of the researcher, but does not include cash cost.
7. Risk Management Plan (~700 words)
7.1 Approach
Risk is controlled by a cycle of Identify, Assess, Respond and Monitor. Risks are entered into the progress and risk log (Section 6.1) every fortnight and discussed at monthly supervision meetings. Each risk is rated according to likelihood and impact (1-5 each), and the resulting score is classified as: 12 or above is high; 6-11 is medium; 6 or below is low. Named triggers are given to high risks, and action begins on a signal, not when it is felt there is a problem.
The risk issues in a DBA are different from the risk issues in an organisational project. Many of them are from the researchers' own lives, e.g. working full-time and studying part-time, and from reliance on the participation of others who have no responsibility for the researcher.
7.2 Risk register (illustrative)
|
ID |
Risk |
L |
I |
Score |
Response |
Mitigation and contingency |
Trigger |
|
R1 |
The manager of a small or medium enterprise refuses or is unable to be interviewed. |
4 |
5 |
20 |
Reduce |
Employ tactics to recruit early, including professional networks and SME support bodies; provide a summary report as an added value; back up with 12 interviews followed by documentary evidence. |
Less than 5 interviews scheduled by Month 15 |
|
R2 |
Low respondents to the survey |
4 |
4 |
16 |
Reduce |
Pilot survey, keep under 15 minutes, send two reminders, many distribution channels, reduce target to 120 responses if necessary, noting reduction of analytic power. |
The number of responses for the first 17 months was <60. |
|
R3 |
Time spent by researchers that is squeezed out due to work or personal obligations |
4 |
4 |
16 |
Reduce |
Reserve two fixed weekly blocks of study time, be flexible with employer, leave float for survey time. |
If a target is missed for two months in a row. |
|
R4 |
Ethics approval delayed or conditions imposed |
3 |
4 |
12 |
Reduce |
Complete application early; use the pilot to make consent materials more precise; meet with ethics committee before submitting the application. |
Failure to decide within 6 weeks. |
|
R5 |
Adding features or new AI tools (scope creep) |
3 |
3 |
9 |
Avoid |
Stay within scope; use the change-control rule; write new ideas on a future research list. |
Any request that has an impact on a milestone. |
|
R6 |
The findings are always out-of-date because of the rapid evolution of Generative AI |
4 |
3 |
12 |
Accept and monitor |
Focus findings on management practices, rather than on specific tools, which age at a slower rate; keep the literature scan up to date before thesis submission. |
New major tool category appears. |
|
R7 |
Loss of information or breach of confidentiality |
2 |
5 |
10 |
Reduce / transfer |
Encrypted storage, anonymised transcript, automatic backups, GDPR compliant data management plan |
Any security incident |
|
R8 |
Supervisor not available or has changed. |
2 |
4 |
8 |
Reduce |
Determine who the second supervisor will be from the beginning and maintain a written record of each meeting; |
Failure to attend two consecutive months |
|
R9 |
Assumptions or inadequate analysis by the researcher |
3 |
4 |
12 |
Reduce |
Triangulation of the following tools: reflective journal, second coder check on 20 % of interviews, methodological triangulation |
Low inter-coder agreement |
|
R10 |
Cost overrun |
2 |
3 |
6 |
Accept |
10% contingency; spend first what is considered must-have. |
Spending is 10% over budget at Month 20. |
R1 is the most critical risk, and it resides on the critical path as part of interview collection (A7). The compromise is then important because, if the full goal is not reached, the goal for Month 21 is still attainable. Agreed fall-back of 12 interviews – as per the data requirements section, which also classed interviews as a must-have; as a result of this, this was designed to ensure the integrity of the study, though not necessarily the schedule.
7.3 Life-cycle challenges (AC 4.1)
Examining the project through its life cycle shows that different challenges dominate at each stage.\
|
Stage |
Typical challenge |
How the plan responds |
|
Initiation |
Selecting a topic that is too general or has no specific gap in the knowledge about it. |
Narrow scope, tutor approval, SMART objectives |
|
Planning |
Misjudging times, particularly ethics and recruitment. |
Float analysis, 10% cost contingency, early ethics submission |
|
Execution |
When it comes to participation, motivation over the long term is a problem. |
Development of the theory of early recruiting, fixed study blocks, parallel survey work and interviews. |
|
Monitoring and control |
The drift out of the plan was not noticed; scope creep |
Fortnightly log, milestone gates, change control |
|
Closure |
Too little and too late, thesis writing and dissemination. |
This involves the initial drafting of chapters (A13) and the journal article planned in the schedule. |
7.4 Best practices (AC 4.2)
The plan incorporates six practices that are considered good project management in research:
7.5 Recommendations for successful delivery (AC 4.3)
Use the critical path as priority. Hold off on nothing until after ethics approval, especially in interview recruitment – begin the process as early as the rules allow (e.g., create a list of interested contacts).
Use floats deliberately. The survey path is a limited resource which lasts four months. Use it when the critical path is in danger; don't let it go by unnoticed.
Agree fallbacks early. Minimum viable sample sizes should now be determined with the supervisor, but not when pressure is applied.
Check progress in the plan every 4 months. Test the remaining schedule every three months and tweak as necessary, as a 36-month course cannot be correct at the outset.
Plan for wellbeing. When you are a part-time DBA, researcher fatigue is a real threat to delivery and needs to be accounted for, so plan for rest breaks, and don't overwork yourself.
This is an example of one of the assignments in the OTHM Level 7 Diploma in Strategic Management and Leadership Practice Unit Project Development, Planning and Management. These are sample answers to the OTHM Level 7 Diploma in Strategic Management and Leadership Practice unit Developing Strategic Management and Leadership Potential. By reading through this sample, you will notice how to answer these questions and the academic voice and writing style you will emulate for your best marks. The following sample will help you get an idea of what your tutor expects to see in your assessment. There are points in these answers which you can go over and write your answers according to them, but these questions are not easy to understand and require critical thinking. Please do not copy/paste the same information. If you need OTHM assignment writing assistance, you can take help from this sample. This is the time you can rate our writers who have been helping to write OTHM assignments for the last 8 years. They are knowledgeable and competent in helping students; you can assess their skills, as this assignment sample for OTHM Level 7 is also written by such people. They possess knowledge which can aid you in achieving good grades. They have an understanding of the standards of OTHM, marking guidelines and structure which have to be observed when composing these assignments. So, if you're occupied with some other work and feel that you require some professional assistance, then you can simply reach out to us and avail help from our best assignment writers.
Get Your Free Academic Quote
No hidden fees · Instant response · 100% confidential
Let's Book Your Work with Our Expert and Get High-Quality Content