W1 Discussion – Your PM Chosen Topic Please pay careful attention to

W1 Discussion – Your PM Chosen Topic

Please pay careful attention to the grading rubrics for the discussion forum.

A minimum of two responses to fellow students must be posted on separate days. This will earn you a grade of B. You must exceed the minimum to earn full credit.

Your insights from the literature readings are essential, and we would like you to share them with the class as much as possible. 

Discussion postings should be approximately 150-300 words. Communicate in complete sentences, concise, focused paragraphs, and precise language. Excessively wordy postings are not an advantage, but overly brief postings have little to contribute to the discussion. Provide adequate support for your postings; simply agreeing or disagreeing with your colleague is not appropriate. Be detailed and support your response with evidence.


1. Primary Post: Post at least one primary response.

Choose a topic that interests you from the list of general topics provided below for this course to investigate. This will be the main topic you will focus on and research about for the rest of this course, so choose wisely. Please remember that you will have to submit a final paper in Week 6. The final paper is based on your weekly discussions, and it should be your cumulative work from week 1 to week 6. Please refer to the final paper assignment link for more details and examples.

For this week’s discussion, at a minimum, your post should provide:

A brief description of the topic you chose to help the reader understand what you are talking about (assume the readers do not understand the topic).

Why did you choose this topic?

Why is it important to investigate?

What is the practical importance/implication of this topic you chose to the general project management practices?

Provide specific question/s you want to have an answer for by the end of your investigation/research.

2. Secondary Responses: Post at least two of your secondary responses to other students’ discussions no later than Sunday evening by 11:59 pm of the same week.

For any two of your classmates’ primary posts, please provide your feedback on their topics by asking questions and professionally critiquing the investigation questions.

Course topics to investigate:

Project needs assessment and planning project scope

Project requirements and elicitation

Requirements Management 

Work Breakdown Structure (WBS)

Scope Creep

Scope Management 

Scope control

Scope planning and the different project development approaches

 Other related topics with instructor approval

Databases to use:

Web of Science





Other peer-reviewed journals

Note: These and others are accessible from the NU Library: https://library.northeastern.edu/research/resources/a-to-z-index (Links to an external site.) 


Sample of PM journals:

Project Management Journal

International Journal of Managing Projects in Business

International Journal of Project Management

International Journal of Project Organisation and Management

Journal of Engineering, Project, and Production Management

Journal of Engineering and Technology Management

Other useful sources:

https://libanswers.snhu.edu/faq/8772 (Links to an external site.)



The topic I chose was project requirements and elicitation.  This is essentially the first phase in any project as it helps establish the standards by which the project will be graded against to be considered successful.  It helps set the left and right limits of what work is to be done throughout the project (Walker, 2013). Not having clear requirements or methods for drawing them out can lead people to chase just about any ‘good idea’.  This can cause cost and time overruns, team member burnout, and overall project failure.

     It’s also one of the hardest steps as project managers and teams need to be able to help the project sponsor align the project’s goals with the overarching mission and vision and translate said requirements into workable aspects (Walker, 2013).  This requires a fair amount of knowledge and experience across and array of topics and capabilities.  It’s a combination of both art and science (Walker, 2013).

     There are three main questions I’d like to have answered through this upcoming research.  First, what are the most effective methods for eliciting requirements?  Next, how does the project team align project requirements with the organization’s vision and mission?  Finally, what are some effective way to producing clear and concise requirements so as to prevent scope creep later in the project.



Walker, L. W. (2013). Requirements—shmirements!: let’s just do it! Paper presented at PMI® Global Congress 2013—North America, New Orleans, LA.

     Newtown Square, PA: Project Management Institute.


For my research this semester, I am going to investigate factors and causes of scope creep and find tools that can be used to reduce scope creep. According to the PMBOK Guide Seventh Edition, scope creep “…is when additional scope or requirements are accepted without adjusting the corresponding schedule, budget, or research needs. To combat scoop creep, project teams use a change control system where all changes are evaluated for the potential value they bring to the project and the potential resources, time, and budget needed to realize the potential value” (87). The specific questions I want to answer by the end of my research are:

What are (some of the) common factors and causes of scope creep?

What tools are used or have been used to combat scope creep?

Because projects are always unique, project teams have an ongoing need to assess possible threats to project success with scope creep being just one of those threats. While I know what scope creep is, I want to learn more about factors/causes and prevention tools that I can apply to the kind of work I expect to see when I start working on projects. Last semester, I found a way to intertwine my research with a previous project example at work and I intend on doing the same for this project. I look forward to having the opportunity to do this again because each time I research I am building a tool to use in future projects. 

Project Management Institute. (2021). Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.