Northlake College Mapping CMMI Process Areas to Agile Best Practices Bibliography

User Generated

fncan999

Business Finance

Northlake college

Description

This paper has a 3 parts. Please open an attached pdf file and read instruction carefully then bid on this paper.

1. Topic selection

2. Annotated Bibliography and

3. Final Paper.

Unformatted Attachment Preview

Course Literature Review Assignment The course Literature Review, worth 30% of the overall course grade, is a 1213 page (approximately 3,250 words - excluding title, abstract, and reference list) double spaced APA 7.0 compliant literature review of a course relevant project management topic. The assignment consists of the following three assignments: 1. Topic Selection: This is a 2-3 page overview of the Topic you are choosing for your paper, worth 15% of overall grade. Due by Saturday of Week 3 at 11:55 PM Central (see the Week 3 course module for details). 2. Annotated Bibliography: This is a short review of key sources you will review for your paper, worth 15% of overall grade. Due by Saturday of Week 6 at 11:55 PM Central (see the Week 6 course module for details). 3. Final Paper: Worth 70% of the course research project grade, due by Saturday of Week 8 at 11:55 PM Central (see the Week 8 course module for details). Assignment Description A literature review is a discussion of the published information in a particular subject area. It should be a critical evaluation of sources (primarily scholarly articles) on a certain subject that highlights the relationships between the various writings and how they relate to your own knowledge and understanding of the topic. Do not consider a literature review a simple summary of an unrelated group of articles. A good literature review will look at the research that has been done and synthesize or pull together those elements that are similar or most pertinent to the theme you have chosen. IMPORTANT: A literature review is a discussion of the published information in a particular subject area. This is NOT intended to be just a discussion of key topic areas, but a synthesis of the research you have uncovered and key findings from articles reviewed. Assignment 1 -- Topic Selection: *Due by Saturday of Week 3 end of day (11:59PM CST). See Moodle course description for more detail. a) Topic Selection Details Select a project management topic from the course topics listed below. Then prepare and submit a one/two page (~ 450 words), double spaced, APA 7.0 compliant, paper describing your topic, why it is important to you and what you expect to learn from researching the literature on your topic. Submit your topic description paper by selecting “Add Submission” in the Moodle Literature Review b) Topic List Select a project management topic from the course topics listed below, OR please contact me with another area not listed here that you would like to cover. You can select a topic group or an individual subtopic; just select something you will enjoy reading and writing about. Then prepare and submit a one/two page (~ 450 words), double-spaced, APA 7.0 compliant, paper describing your topic, why it is important to you and what you expect to learn from researching the literature on your topic. Submit your topic description paper by selecting “Add Submission” in the Moodle Literature Review – Topic Selection assignment dialogue by Saturday of Week 3 at 11:55 PM Central Time. • • • • • • • • • • • • • • • • • Agile History The Agile Manifesto Agile Lifecycles The Agile Mindset and Definition of Done Overview of Agile Frameworks Agile Scrum o Best Practices o Key Tools & Techniques Agile Stakeholder Development o Best Practices o Key Methods, Tools & Techniques Agile Knowledge Transfer Agile and Organizational Change Management (OCM) The Kanban Method o Best Practices o Key Tools & Techniques Agile Value-Driven Delivery Agile Value Stream Mapping Extreme Programming (XP) o Best Practices o Key Methods, Tools & Techniques Agile Adaptive Planning Agile Teams: Composition, Performance, Evaluation o Best Practices o Key Tools & Techniques Agile and the Program/Project Management Office (PMO) Feature-Driven Development (FDD) o Best Practices • • • • • • • • • o Key Tools & Techniques Dynamic Systems Development Method (DSDM) o Best Practices o Key Tools & Techniques Crystal Method o Best Practices o Key Tools & Techniques Agile Estimation & Planning o Best Practices o Key Tools & Techniques Agile Problem Detection Agile Problem Resolution Agile Earned Value Management Agile Budget Tracking Hybrid Agile – combining Agile and traditional (Waterfall) methods, tools & techniques Other (Please contact instructor for a specific topic that interests you within Agile Methods) c) Topic Selection Scoring Guide Activity Identifies a project management topic that is relevant to the text as a proposed topic. Explains why the selected topic is of interest or significance in relation to the course. Demonstrates significant compliance with APA style. Total: Percent 40 40 20 100 Grade Conversion for All Grades: Percent Grade 92-100% 82 – 91% 72-81% 62-71% 0-61% Letter Grade A B C D F Assignment 2 – Annotated Bibliography: *Due Saturday Week 6 end of day (11:59 PM CST). a) Annotated Bibliography Details Prepare an annotated bibliography that is APA 7.0 style and format compliant, listing at least FOUR sources that you have located and evaluated for your project (NOT including assigned class texts). An annotated bibliography is a bibliography that includes a summary of the research that you have done. It is an alphabetical list of research sources with the addition of a brief summary or annotation. The annotation usually contains a brief summary of content and a short analysis or evaluation. In order to write a successful annotation, each summary must be concise (100-250 words) (do not copy the abstract) and the annotation should display the source's central idea(s) and give the reader a general impression of what the source is about. The annotation should also contain a statement regarding the applicability of the source to the researcher’s topic of interest. Avoid ‘popular’ websites such as USAToday, Yahoo, etc. Business or Academic websites are acceptable such as CIO.com, Harvard Business Review, etc., or research articles from universities or academic journals. Your focus should be on scholarly or business research, not news sites; these will not be accepted as valid articles for review. You may choose business or academic books, but I recommend avoiding writing your paper on too much content that would exceed your topic; there is not enough room to cover all this information in a 12-13 page paper. If you have a specific book to use, focus on specific chapters that relate to your topic. Literature Paper and Class Texts (including PMBOK): The focus of this assignment is on external research. References to our class texts are acceptable (including PMBOK). For example, it is acceptable to note that you find key differences between PMBOK methodology and the research article. However, note that the paper should NOT be an exhaustive comparison of your chosen articles and PMBOK / class texts. Instead, your focus should be on key findings from your research articles. Compare and contrast key findings between articles if possible. For example, does author A agree with author B? Why or why not? b) Annotated Bibliography Scoring Guide Activity List at least FOUR references (not including assigned course texts). Include concise summary of each reference. Include a SHORT analysis or evaluation of each reference. Include a statement regarding the applicability of the source to your topic. Demonstrate significant compliance with APA style. Total: Percent 10% 20% 30% 30% 10% 100% Assignment 3 – Final Literature Paper Due *Due Saturday Week 8 end of day (11:59 PM CST). You are requested to write a 12-13 page, APA 7.0 compliant, literature review of the current literature covering your topic. Literature Review Paper Requirements: a) Structure: The paper should include 3 main sections: 1. An introduction, giving the reader a quick idea of your topic, your thesis or problem statement, and the central theme or organizational pattern you will follow. 2. The body, which contains your discussion and synthesis of source material. 3. A conclusion and recommendations, in which you posit what you have learned from your literature review, what questions it raised for you, how you plan to proceed, or what seems to be missing from the research. b) Number of Pages: 12-13 double-spaced pages, not including the title page, abstract, & reference pages (approximately 3,000 words). c) Paper Writing Guidelines: Write your paper for "the intelligent layman:" Write your paper assuming that your reader will be intelligent but may not be familiar with your topic and/or industry. This means that you should explain any technical concepts, avoid jargon and explain acronyms before using them. Avoid first person: First person point of view is often used in personal narrative—when the writer is telling a story or relating an experience. This perspective is the writer’s point of view, and the writer becomes the focal point. First person personal pronouns include I, we, me, us, my, mine, our, and ours. Writing from the first person point of view can, at times, weaken the credibility of the writer in research and argument papers. When the paper is written in first person, the work may sound like it is based only on personal opinion. Weak: “I am writing this paper to let you know how bad I think bullying is.” (1st person) Stronger: “Bullying is a social issue that may result in devastating physical, mental, and emotional consequences for its victims.” (3rd person) d) Final Draft Details Submit the final draft of the Literature Paper by selecting “Add Submission” in the Moodle Literature Review – Final Draft assignment dialogue. e) Final Course Project Assignment Scoring See Scoring Rubric below. The Final Paper counts for 70% of the overall literature review assignment grade. Activity Key Approach to the Paper: Successful review of EXTERNAL RESEARCH of your topic, SYNTHESIS OF KEY FINDINGS AND RECOMMENDATIONS from each study. Provides a logical defense and support of your positions using external reference and empirical data. Demonstrates grasp of course concepts and theory and their application to the student's chosen topic. Applies course text material to the literature reviewed. Communications: Free of errors that detract from the overall message. Good writing mechanics including proper sentence structure, paragraph structure, grammar, punctuation, and spelling. Main supporting points easily identifiable, plausible, sophisticated, insightful, and clear. Avoids firstperson language. Written for "the intelligent layman." Sources: At least FOUR additional scholarly sources (in addition to course texts); these sources can be books, journal articles, and/or (no more than two) online websites. Title Page / # Pages / Structure: 12-13 double-spaced pages, not including the title page, abstract, & reference pages (approximately 3,250 words). Includes a title page with the title, date, course number and name, instructor’s name and your name. Put Student Name within the file itself before submitting, such as "J Smith Risk Management.doc." APA Style & Citations: Proper and effective use of APA 7.0 compliant citations and in-text references. Total: % of Total Grade 40% 30% 10% 10% 10% 100% APA Formatting: Refer to the following website recommended for basic APA formatting and guidelines: https://owl.purdue.edu/owl/research_and_citation/apa_style/apa_formatti ng_and_style_guide/general_format.html *Note APA has recently changed to a new 7th edition, refer to table below for key differences: 6TH Edition 1. Include the location of the publisher in the reference. 2. In – text citations are listed for 3+ authors by using et al. 3. List up to 7 authors in the reference. 4. DOIs were included in the URLs. 5. Include the word “Retrieved from” in front of the URL. 6. Include the format, platform, or device for eBooks. 7. Do not cite contributors. 8. Online sources cited. 9. No insertions for biases info, gender, age, identify. 10. Use labels. 11. Use approximate measures. 12. More sample pages: Times New Roman preferred but acceptable: Calibri/Arial. 13. Simplified running head. 14. Running Head was included on student papers. 15. Levels were written in bold. 16. Vacillate from 1 to 2 spaces but consistent. 7th Edition Do not include the location of the publisher reference (city and state excluded). Shorten in- text citations initially for 3+ authors by using et al. Surnames for 3+ authors are not listed but the surname of the first author with et al. List up to 20 authors in the reference. Use DOIs as URLs. Do not include “Retrieved from” in front of the URL unless a retrieval date is needed. Do not include the format, platform, or device for eBooks. Cite contributors. New examples for online source types. Use singular “they” as a genderneutral pronoun. Use descriptive phrases instead of labels. Use exact ranges and not approximates. Acceptable: Calibri 11, Arial 11, Lucida Sans Unicode 10, Times New Romans 12, Georgia 11 Do not need to include the word “Running Head. Running Head is omitted in student papers. Only require page numbers. Updated heading styles. Space 1 time after the period. 17. Italics were used to emphasize. Use double quotation marks for linguistic examples.
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached.

1

Agile Stakeholder Development: A Literature Review

Date
Course Number
Course Name
Instructors Name
Student Name

2
Agile Stakeholder Development: A Literature Review
At present, the agile method has advanced project management in many
organizations. Agile project development can be referred to as a concept of a framework that
responds fast to the collaborations with clients, responding to changes in an organization, and
covers the least amount of documents needed. An agile stakeholder is a person and
organization units that frequently interact with the organization's management, scrum
masters, and scrum teams to help them with the inputs and facilitate the creation of the agile
project services and product, influencing the development of the project. Agile methods help
to enable project development by making incremental and iterative processes and hence
reducing the risk. This literature review paper covers agile stakeholder development in
organizations by looking at some of the best practices, the key methods, tools, and
techniques.
Best Practices
Agile stakeholder development approaches are much more demanding than it may
appear at first glance. A companywide adoption of agile methodologies reveals a positive
attitude and experience towards the agile stakeholder approach, while a small number wanted
to back to the traditional system. Gregory et al. (2015) study emphasized the organizations
that have successfully implemented agile methodology's continued deployment but still faced
challenges and impediments to overcome. The obstacles they identified were in 4 sections of
crucial challenges to agile development and their remediation strategies. For instance, (a) lack
of good communication within the organization setting expectations that are not agile
methodology supported (b) lack of willingness from the management to accept lesser control
over teams, (c) providing reports of expectations for time, and the working budget
estimations are still connected to the expectation of the traditional methods. Nonetheless, the

3
researchers failed to give recommendations for best practices that could be put in place to
counter the challenges they had stipulated in their work.
On the other hand, Sánchez (2018) came up with the remedies to the challenges which
served as the best practices for good agile stakeholder engagement and development. The
researcher pointed out (a) the establishment of clear communication rules and regulations,
plans, and terms; (b) ensuring both the management and the stakeholders undergo agile
training to ensure the expectations are appropriate and reasonable, and (c) ensuring that all
agile methods have the full support of both parties before its deployed as the best practices to
agile methodology.
In addition, according to Gandomani and Nafachi (2015), the agile deployment
framework is the best method for deploying the agile methodology. The agile framework
method provides a systematic process designed to lead a group by deploying the agile
approach in an explanatory manner. The group members can select either one or more agile
methods, which is preferable to them with the project at hand, and then introduce and use the
new approach. Further, in their work, Gandomani and Nafachi (2015) discuss some of the
essential requirements for agile transition in organizations project. Among them, (1) having
compelling reasons to convince the stakeholders for moving to the agile method. (2) The
need to define the project goals clearly to the clients as necessary. (3) Initial training is
essential because the agile approach offers different values from traditional methods; the
stakeholders should learn new activities and focus on recent achievements. (4) an assessment
would follow this during the pre-start-up stages. This section's research offered a clear path to
the agile approach's success in the project and stakeholder development; hence, the content
was vibrant and insightful.

4
According to research carried out by Madampe (2017), organizations perform best
when the management of the process of the project is efficient and straightforward. The use
of non-bureaucratic methods in running projects allows companies to respond to the
customers' needs faster and with flexibility. Hence, this will enable organizations to be in a
better position to compete. Madampe (2017) further asserts that there should be daily, weekly
and monthly updates on the project's progress and status in the agile method of project
management. This allows the stakeholders to fine-tune their needs to get their desired goals
accordingly. Because the consumers are also considered part of the agile team, it develops a
better transparency level. It enhances more significant input from the stakeholders throughout
the project development process. Besides, Runtung et al. (2020) reported that a good
communication flow between an organization's management and the stakeholders allows for
a project's success. Their study suggested a web-based application that can be used on
communication between the two parties.
The presence of iterations, if any problem occurs in the process, it can be fixed in the
early stages and reduces the possibility of repeating in the later stage. In circumstances where
some things may be missed, they will be found and corrected at frequent demonstrations, and
then the agile project team members can take precautions. The efficiency in project
management makes an agile method to help save the project's cost by identifying the
loopholes or adjusting problems early (Madampe, 2017). The researcher also adds that as a
best practice, regular meetings with the stakeholders increase the relationship between the
two parties and helps to focus on improving the project as one team. This allows for the
cross-functional team in an agile project to solve their many problems easily and quickly.
Further, Madampe (2017) states that some of the managerial concerns have to be addressed
before adopting agile project management at the management level.

5
Compared to the traditional methods, which operate in predictable ways that are easy
for the teams to plan projects, formulate budgets, and allocate resources, the agile
methodology focuses more on the value. Karvonen et al. (2017) add that agile teams are
multi-functional, and the teams have skills and knowledge in different areas apart from the
ones they are specialized in. The customers feeling about the agile project management
method not being successful and might waste their investment should be handled by making
them aware of the agile method's importance and value in project management. Madampe
(2017) outlined several best practices that should be considered to make the agile project
management best. For instance, the author stated that the manager's role in traditional
concepts should be altered to show the team members' right direction creatively and
innovatively. Also, the ability of resources to be spread in different geographical areas should
be tackled by the team members to overcome the challenges and keep the methodology.
Education should also be offered to the team members to understand the agile method; this
reduces misconceptions about the agile approach.
Therefore, the agile method has a highly interconnected group of practices that work
together to achieve an agile project's value. Looking at the best practices affirms the
understanding that the managers need to learn and adapt their teams' practices to enhance
agile development. Therefore, some of the best agile stakeholder development practices are
daily meetings, customer collaborations, iterative development, sprints, and reviews.
Key Methods
The process model and pr...


Anonymous
Just what I needed…Fantastic!

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Similar Content

Related Tags