After reading this article about gathering and analyzing project requirements, write an initial post in which you share an experience where you had to collect business data. Explain what method you used to collect it. Why did you select this method over others?
When responding to your classmates, answer the following questions: Do you feel a different data collection method could have worked better? Why or why not?” (TWO (2) PARAGRAPHS EACH WITH REFERENCES ON EACH OF THEN NOT TOGETHER)
Please view article here http://web.archive.org/web/20150110053317/http:/www.pmi.org/~/media/PDF/Knowledge%20Center/PM%20Network%20Requirements%20Article.aspx
1.Hly Ftz Pro Spn Frm H
In a previous life, I worked as a senior project manager (PM) for an oil and gas company. I was the project manager that stepped in and picked up the pieces when a project was breaking the triple constraint or had unhappy stakeholders (Haughey, 2011). One of the last projects I worked on was a software development project that was months late, over budget, and had an unhappy sponsor. This sponsor believed that the project team had not delivered the initial scope for phase one of the project.
After interviewing the outgoing PM, the project sponsor, and the development team I realized that the sponsor’s requirements, while discussed, were never documented. Once a month the sponsor would meet with the development team and talk about what the sponsor wanted. The development team would then do three weeks of frantic coding based on what they remembered of the discussion. In the fourth week, the sponsor would review the completed development and provide feedback for the meeting with the development team the following week. Then the wheel of pain would start over.
I quickly realized that project was going nowhere because the sponsor’s requirements were never documented or even fleshed out. This was exacerbated because the project sponsor had the attention span of a flea and was hard to pin down to a decision. Every requirements discussion was a new beginning, with the sponsor frequently contradicting themselves. I used the value engineering method to restart the project, focusing on requirements gathering (Gale, 2013). I worked with the sponsor to identify subject matter experts (SMEs) that they trusted, then organized a series of workshops with the SMEs to define project scope and create a requirements document. This put the responsibility for the detailed requirements on the primary users and relegated the project sponsor to high-level decision making.
From my perspective as a PM, it is best to pick and choose from different project methodologies. Rarely does the requirements gathering phase only use tools from a single type of analysis. Because of the difficulties with this particular sponsor, I used aspects from other methods of requirements gathering. From the Lean method, each requirement had a specific definition of success to prevent the sponsor from rejecting the requirement due to last minute, undocumented requests (Gale, 2013). I also borrowed from the Agile methodology and prevented scope creep by strictly defining what would be delivered in the first iteration. The ever-increasing list of sponsor “requests” (read “demands”) were placed on a list for future development iterations, to be evaluated and prioritized using the systems engineering approach of assessment based on budget, time, scope, risk, and impact (Gale, 2013).
2.Ars Autn). Buz and tech reqment
As a Solutions Engineer for a telecommunication company there are steps we have to take an order to get a customer up & running. One of the steps is gathering the needed information from the client about the opposing order. For instance:
For example: When we have a new customer like Target (example), and they want to bring their sites to us, we have to gather background information about the client and see what it is they are expecting from us. We have to ask questions about their stores, how much data they use on the regular, are they giving us control of their sites, do they plan on managing their sites on their own. Once this information is gathered, we are now able to present solutions for them and their design with us.
Since I work on the wireline enterprise side I do not necessarily care about the number of employees; I am concerned about how much traffic will be going on the network from this site, how any devices if any, do you need TN number if so how many? These are all the questions I need before we can proceed with the order. We have a COT form where their Account Manager fills out all the relevant information for the site : (Site address, Site Contact Info, Services, Contract Terms, etc..)
Granted I have made it sound simple, but it is not when dealing with customers who do not have the right personnel in place, so sometimes you will get the run around for IP addresses or even the exact location of the site.
3.Trll Brns). 2:1 dis
During my career with the phone company my most favorite is assembling a focus group. The main part is gathering the correct people who have the same purpose. We had to roll out a new productivity measuring tool to implement metrics for non-management personnel. The program was titled MSOC management system operating controls. We performed riding exercises not in a vehicle as one may think, but over the shoulder timing all tasks throughout the cycle of provisioning and order from start to finish. We used stop watches and PDA’s to set the time per task for center personnel.
We measured several employees and across multiple centers and then performed a data dump, Then, we gathered and complied new data with historical data functions. The implementation teams created key activities and key measurements and this method proved to be successful. The focus group method is very useful because one can get many views, and allows for the study of the dynamics of a situation, frequency counts of target behaviors, or other behaviors as indicated by needs of the evaluation. Can produce qualitative (e.g., narrative data) and quantitative data (e.g., frequency counts, mean length of interactions, and instructional(2017) …My favorite two methods are focus groups and observations these both in the past have been great tools to gather project information.
PLEASE READ THIS.IT IS VERY IMPORTANT
Allow your discussion posts to be detailed and capable of sharing knowledge, ideas and points. You must discuss the topic using your own words first. Using your own words indicate you understand the topic of discussions. Secondly, you must cite your sources in-text. This is necessary to justify your points. Sources from several sources showed good research abilities. Lastly, you must provide references at the bottom of your post. A discussion post without justification with sources does not show proper research abilities. A terse and not detailed discussions represent post that would not provide enough sharing of knowledge or proper understanding of the topic. DO NOT just copy and paste a sentence from online with citation at the end as your own discussion. I have not asked for definitions, I asked for discussions and will not buy this. You must show understanding of the discussion topic by using your own words to describe the topic and then justify that with sources.
www.citationmachine.net to format references into the APA style if necessary. Extremely important. Intext citations is very essential and highly needed as well.
use double spacing, 12-point Times New Roman font, and one-inch margins. Sources should be cited according to APA citation method (citation should be relevant and current). Page-length requirements:2 PAPARAGRAPHS FOR EACH PROMPT ANSWER. Make sure you cite if you take a piece of someone’s work, very important and your reference should relate to your writing (don’t cite a reference because it relates to the course and not this very paper) at least 2 current and relevant academic references. No heavy paraphrasing of others work.
