Note Read The Case Scenario And Instructions Given Below

Noteread The Case Scenario And Instructions Given Below And Write 3 4

Note: Read the case scenario and instructions given below and write a 3-4 page answer on the following instructions. Must include 3-4 scholarly references cited in APA. Your answer must be 100% original.

Instructions: Case Scenario: Sheet1 (2) WBS Level WBS Code WBS Element Task descriptions Resource Skillset Predecessor 1 1 Website Design WBS 2 1.1 Apply for domain name Kippley 2 1.2 Apply for website space Jhon 2 1.3 Website position All the team member 2 1.4 The analysis of website function and requirement. All the team member 3.4.1 Discussion board function Robert 1..4.1.1 Create a thread function Russel 1..4.2 Learning center function Robert 1..4.3 Company culture function Russel 1..4.4 Daily News function Jhon 1..5 Website style design Ramesh 2 1.6 Website production All the team member 3 1.6.1 Coding Using Java Coding All the team member 1..7 Webiste program nesting Jhon 2 1.8 Website testing Aaron 1.81 Function testing Test each function Aaron 1..9 FTP upload Jhon 2 1.1 Website maintenance Robert and Russel and Aaron &C&"Arial,Italic"&9Practice Standard for Work Breakdown Structures&"Arial,Regular"—Second Edition ©2006 Project Management Institute Bicycle WBS Sheet2 Sheet3 Sheet1 (2) WBS Level WBS Code WBS Element Task descriptions Resource Skillset Predecessor Cost/ hour 1 1 Website Design WBS Define scope $80. days $12,800..1 Apply for domain name Jeevan Identify high level roles $80.00 $1,920..2 Apply for website space Ramesh Develop high level budget $100.00 $2,400..3 Website position All the team member High level control startegies $100.00 $2,400..4 The analysis of website function and requirement. All the team member draft project charter $100.00 $3,200..4.1 Discussion board function Wanjun Consolidate project charter $100. $800..4.1.1 Create a thread function Wanjun Revise project charter $100. days $1,600..4.2 Learning center function Shashank Finalize project charter $100..4.3 Company culture function Raja Develop work break down structure $100.00 $11,200..4.4 Daily News function Jeevan develop project schedule $100.00 $4,800..5 Website style design Ramesh develop project budget $100. days $4,800..6 Website production All the team member develop communication plan $100.00 $3,200..6.1 Coding Using Java Coding All the team member develop quality management plan $100. $3,200..7 Webiste program nesting ME. Initial assesment on IT structure $120. days $1,920..8 Website testing Jeevan and Wanjun Define desktop application support services $120.00 $4,800..81 Function testing Test each function Raja and ME. Define server administration services $120.00 $4,800..9 FTP upload Wanjun Define network administartion services $120.00 $8,640..1 Website maintenance Raja, Jeevan and ME. Assess security requirements $120.00 $4,800.00 Perform security requirements $120.00 $7,860.00 Strategic planning on various IT services $120.00 $1,920.00 Test the desktop application supprot services $120.00 $3,200.00 Test the server administration services $120.00 $3,200.00 days Close the project Conduct post project review $100.00 $3,200.00 lessoned learned $80.00 $3,200.00 documentaion and knowledge transfer $80.00 $6,400.00 Project cost $106,260.00 Assumptions: 5 days work week Holidays not included 1 day - 8 working hours COST: $80 per analyst $100 for PM $120 for developers &C&"Arial,Italic"&9Practice Standard for Work Breakdown Structures&"Arial,Regular"—Second Edition ©2006 Project Management Institute Bicycle WBS Sheet2 Sheet3 Scope Statement Executive Summary / High Level Description Salesforce is one of the cloud service provider on infrastructure as a platform. Salesforce is going to open a new website for their employee’s community to learn about the new concepts. This website has the functions of maintaining interaction with each other and can improve communication while learning. The website may contain the blocks like culture, education, new concepts in technical and management etc. Problem Statement The organization wants to bring some changes into employee’s working environment. So it decides to implement a project in order to bring all people at one platform and can exchange their views and thoughts. To overcome the above problems, Salesforce organization decides to make a website for their employees. Approach (optional if only one phase): Initial phase: Define the project, get the defined requirements from the project. Document all the information into Project Framework and Project Charter. Planning phase: Have a detailed planning including the schedule, resource locate. Development phase: Start website development: design, coding,testing, verifying, releasing, maintenance. Close phase: Document all the files and write a analysis report. Key Deliverables Detailed Description Schedule, resource plan. Schedule plan includes whole project processes schedule to make sure we can finished the project on time, which is within 8 months. Resource plan lists how we are going to spend the budget $500000 dollars on the project to make sure we won’t exceed the budget. Data: 07/01/2016 Website initial design blue print The website initial design blue print includes the website functionality,website frame, fond, and format. Date: 07/15/2016 The first version of website The first version of website has some defects. But it is exciting for the team members to deliver the first version of website. Date: 12/15/2016 The final version of website After testing and verifying phase, the final version of website is completed. Date: 2/15/2016 Document all the files Files include the management files, technology files. Date: 03/01/2017 Desired Outcomes –How to Determine Success: we complete the project within time, cost and scope. The website is successfully satisfy the requirements from Salesforce. Employees of Salesforce can learn new technology from time to time through the website, they also interact with each other and exchange views and ideas at the website discussion board. The security and privacy problem at this website are also enforced. The user satisfy rate is 95%. Measurements: Security: Every user has unique ID and password to log into the website. User can log in only both ID and password are right. Only the employee of Salesforce can register the website. Data privacy: User can’t pull out other user’s privacy information. Metric Baseline Measure Target Measure Website response time 0.01 second 0.008 second Data back up period Once a month Every Two weeks Time that help desk resolves problem 1 hour Half hour

Paper For Above instruction

The development of a comprehensive website for an organization like Salesforce involves meticulous planning, structured execution, and coordinated teamwork. This process is well exemplified through the use of Work Breakdown Structures (WBS), which serve as essential tools for breaking down complex projects into manageable tasks. The scenario provided offers insight into the different phases, resource allocations, and cost estimations necessary for building a user-friendly, secure, and efficient website to foster employee interaction and learning.

Project Planning and Scope Definition

The initial phase of the project emphasizes defining scope and setting clear objectives. According to PMI (2006), scope management is fundamental to project success, as it delineates what is included and excluded from the project. In this case, the scope encompasses designing, developing, testing, and maintaining a website tailored for Salesforce employees to facilitate communication, knowledge sharing, and cultural integration. The scope statement provided explicitly emphasizes functionality such as discussion forums, learning centers, company culture modules, and news updates, aligning with strategic goals of fostering engagement and collaboration.

Work Breakdown Structure (WBS) and Task Allocation

The detailed WBS offers a structured breakdown of the tasks with assigned resources and skill sets. For example, applying for a domain name (WBS 1.1) and website space (WBS 1.2) involve resource allocation to specific team members such as Jeevan and Ramesh, respectively. The tasks are sequenced to follow logical dependencies, with predecessors clearly identified to ensure timely progression—this is aligned with the best practices in project management described by Schwalbe (2015). The WBS also includes essential phases such as website style design, coding using Java, testing, and FTP upload, with dedicated resources like Aaron for testing and Jhon for deployment, illustrating an effective division of labor.

Cost Management and Resource Allocation

Cost estimation, based on resource skillsets and hours, is crucial for staying within the project's budget of $106,260. The costing structure, such as $80/hour for analysts, $100/hour for project managers, and $120/hour for developers, guides allocation and helps prevent budget overruns. This aligns with Kerzner’s (2017) emphasis on detailed cost management. For instance, the high cost of developing the work breakdown structure ($11,200) reflects the importance of detailed planning to avoid unforeseen expenditures during execution.

Schedule Development and Timeline Management

The schedule, with deadlines such as completing the initial design by July 15, 2016, and final delivery by December 15, 2016, ensures adherence to the project timeline of eight months. Effective scheduling, including milestones and resource allocation, is crucial for project control (PMI, 2006). The project phases—initial planning, development, testing, and closure—are sequentially aligned to facilitate smooth transitions and timely completion.

Risk Management and Quality Control

Security and privacy are pivotal, given the confidential nature of organizational data. Security measures, like unique IDs and passwords, are mandated, and privacy controls prevent unauthorized data access. Testing phases involving detailed functional testing (Aaron) and security testing emphasize quality assurance, which Schwalbe (2015) highlights as essential to meet stakeholder expectations. Additionally, establishing metrics such as website response time and help desk resolution time enables ongoing monitoring and performance improvements.

Outcome Measurement and Success Metrics

The success of the project is measured by metrics such as response times, data backup frequency, and help desk resolution time. Achieving a user satisfaction rate of 95% indicates the website is meeting its functional and security requirements effectively. As noted by Kerzner (2017), continuous improvement based on such metrics ensures sustained success and stakeholder satisfaction.

In conclusion, a structured approach grounded in WBS, strategic resource management, scheduling, and continuous quality assurance is critical for the successful development of Salesforce's employee community website. The outlined planning phases, combined with clear task dependencies and cost estimations, provide a roadmap to achieve project goals within budget and schedule constraints, ultimately fostering a collaborative and innovative organizational culture.

References

• Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
• PMI. (2006). Practice Standard for Work Breakdown Structures. Project Management Institute.
• Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
• Meredith, J. R., & Mantel Jr, S. J. (2014). Project Management: A Managerial Approach. Wiley.
• Gido, J., & Clements, J. P. (2016). Successful Project Management. Cengage Learning.
• Wysocki, R. K. (2014). Effective Project Management: Traditional, Agile, Extreme. Wiley.
• Larson, E. W., & Gray, C. F. (2017). Project Management: The Managerial Process. McGraw-Hill Education.
• Heldman, K. (2018). Project Management JumpStart. Wiley.
• Cooke-Davies, T. (2002). The importance of stakeholders in projects. Engineering Management Journal, 14(2), 19-24.
• Schwalbe, K. (2018). Managing Information Technology Projects. Cengage Learning.