ComputerScienceExpert
$18/per page/
This in a TermPaper or Research Paper Project . Here is the topic I want you to work on:
The Benefits and Challenges of Agile Methodology in Project Management: Case of Large Software Creation.
Please find general instructions/guidelines in attached files. Here is core/keys points that are require:
1- Paper format: American Psychological Association (APA) with one Inch margin, Times New Roman double space.
TermPap.docTHE“IDEAL”TERMPAPERWell, there might not be one.Then again, what if you could satisfy 1) course requirements, 2) write ona topic that your office could use, and 3) actually increase your knowledge in an area useful to your job?And 4) what if the topic was of sufficient interest and strength that both your boss and your instructorrecommended that you reformat it and present it at an international symposium?All expenses paid (byyour firm, not the Grad School).Not bad for a six to eight page effort (plus Abstract, EXSUM, Table ofContents, etc.).(Note that the work group paper is longer, 8 – 10 pages).First, satisfy course requirements.This means that you should select a topic within the boundaries ofthe course.You have reviewed/previewed/read some of the required portions of the Text (by week 2) andrealize that you cannot write an all-encompassing paper.It would be too broad.Project Management,Systems Analysis and/orIntegration and/or Implementation papers may be on the “technical side” anddeal with the several layers or states leading to convergent integration and systems to systems integration.Project Management, Systems Analysis or Integration papers may also be on the business side and dealwith the business changes that make use of the new technology and training that IT can provide.Wherewill you “spike down” into some detail?Depending on the course, you might consider, for example,testing for systems integration and be primarily concerned with State/Level 2.Perhaps you need todevelop a decision process for software and S/W language selection.Applying a SDLC (SystemDevelopment Life Cycle) Model to a work effortmight be useful in improving a process or solving aproblem.An insightful review of a change management situation might be appropriate.(Again, itdepends on the course).You must also show you appreciate how your detail (the “spike down”) fits intothe continuum of “project management,” “systems analysis and design” or “systems integration” (anothercourse I taught.It is an example, other courses have their own examples).(Incidentally, you could use aless complex Life Cycle from Industry, DOD, or FAA).Your paperrequires a title page, Abstract (at the bottom of the title page), Executive Summary, Tableof Contents with page numbers, and an Introduction.These are explained below.I require these to ensureyou know the difference.Do not confuse the Abstract with the Executive Summary.Abstract – 50 to 75 words.Put this short abstract at the bottom of the Title Page. First sentence –purpose of the paper.Second sentence – methodology used.Third sentence – results of your paper.Fourth sentence, if used– future or additional application of your results; or another recommendation.These short Abstracts are hard to write and must be rewritten several times.The three or four sentencesare “crafted”, not written.A well-written abstract is required in order to submit your paper to asymposium.This course requires a tightly written abstract for both individual and team papers.Again,the shorter than APA recommended abstract is required as symposium produce meeting catalogues. Thesesymposia booklets require short abstracts so all abstracts can fit into the symposia booklet and the longerones can not. If you desire to add a more regular sized abstract, put it behind the title page. The longerabstract may be more useful at work.The Executive Summary is one, I repeat one, page long.A high-level flow chart may be placed on athird of a following page.The first paragraph is the purpose of the paper.The second paragraph is themethodology or research process.The third paragraph (you guessed it) discusses the results and the fourthparagraph provides an evaluation, future use, cost effectiveness statement, request for more funds, etc.Inindustry, you often see a less than one page EXSUM where the purpose is assumed to be known by thereader (after all, he/she authorized you to do the work and report back) and the first paragraph providesthe results followed by the recommendation(s).The EXSUM concludes with the research methodologyand/or any lessons learned.If the paper goes outside your department, then you may have to rewrite theEXSUM into the more traditional form.An EXSUM plus a few other pages will make a fine handout ofyour paper at a symposium.Don’t give away the paper, get their address and make them ask for it.Thus,only hand out the EXSUM, Table of Contents, some charts and “bullets.”Just make up a front/back, onepage handout.The Table of Contents with page numbers is not often used in a less than ten to twelve-page paper.Iuse it, so please include it.The body of most papers should start with an Introduction that sets the reader into a frame of mind tobest receive the information.You tell the reader, succinctly, what is in each section but don’t give awaythe results.Just say the results (or recommendations/findings) are found in section “x”.A “Background”
Attachments: