Task Table: Named Duration, Predecessors, Resources, Notes ✓ Solved
Task Table named duration predecessors resources notes mo
Task Table named duration predecessors resources notes mobile App Plan 34 Days.
Task_Table Name Duration Predecessors Resources Notes Mobile app plan 34 days 3/17/16. Project set-up 7 days 2/1/16 2/9/16. Define project processes 2 days 2/1/16 2/2/16 project manager, product owner. Set up working environment 4 days 2/3/16 2/8/16 3 technical administrator. Determine initial sprint velocity 1 day 2/9/16 2/9/16 4 lead developer. Project setup complete 0 days 2/9/16 2/9/16 5.
Sprint 1 UI 6 days 2/10/16 2/17/16 2. Sprint 1 plan 0.5 days 2/10/16 2/10/16. Select sprint 1 user stories 0.25 days 2/10/16 2/10/16 product owner. Assign user stories 0.25 days 2/10/16 2/10/16 9 product owner, lead developer. Sprint 1 plan complete 0 days 2/10/16 2/10/16.
User Interface 5 days 2/10/16 2/16/16. Design User Interface 2 days 2/10/16 2/11/16 UX developer. Build User Interface 2 days 2/12/16 2/15/ UX developer. Test User Interface 1 day 2/16/16 2/16/ test engineer. UAT of UI 1 day 2/17/16 2/17/ test engineer, product owner. Correct Issues From UAT UI 1 day 2/26/16 2/26/ UX developer.
Sprint 2 reports 15 days. Sprint 2 plan 0.5 days 2/18/16 2/18/16. Select sprint 2 user stories 0.25 days 2/18/16 2/18/16 lead developer. Assign user stories 0.25 days 2/18/16 2/18/ lead developer. Sprint 1.1 plan complete 0 days 2/18/16 2/18/16.
Client Specified Reports 7 days 2/18/16 2/26/16. Design Reports 2 days 2/18/16 2/19/16 reporting developer. Build Reports 2 days 2/22/16 2/23/ reporting developer. Test Reports 2 days 2/24/16 2/25/ test engineer. UAT of Reports 1 day 2/29/16 2/29/ test engineer, product owner. Correct Issues From UAT of Reports 1 day 3/8/16 3/8/16 reporting developer.
Sprint 3 Platform 7 days 3/1/16 3/9/16. Sprint 3 plan 0.5 days 3/1/16 3/1/16. Select sprint 3 user stories 0.25 days 3/1/16 3/1/16 lead developer. Assign user stories 0.25 days 3/1/16 3/1/ lead developer. Sprint 3 plan complete 0 days 3/1/16 3/1/16.
Cross Platform Support 6 days 3/1/16 3/8/16. Design Cross Platform Support 2 days 3/1/16 3/2/16 technical administrator. Build Cross Platform Support 2 days 3/3/16 3/4/ technical administrator. Test Cross Platform Support 1 day 3/7/16 3/7/ technical administrator. UAT of CPS 1 day 3/9/16 3/9/ technical administrator, test engineer.
Project End 2 days 3/16/16 3/17/16. Obtain Final Client Signoff 1 day 3/16/16 3/16/16 project manager, product owner. Provide Project Report Out 0.5 days 3/17/16 3/17/16 project manager, product owner. Project End Celebration 0.5 days 3/17/16 3/17/16 project manager, product owner.
Task_Table ID Name Duration Start Finish Predecessors Resources Notes Project Server 2016 upgrade - waterfall 1. Plan for upgrade to Project Server days 1/25/16 8:00 1/29/16 17:00 Review system requirements for upgrade 1 day 1/25/16 8:00 1/25/16 17:00 Server Administrator, Technical Analyst 3. Plan for clients 1 day 1/26/16 8:00 1/26/16 17:00 2 Technical Analyst, Server Administrator 4. Gather information about your Project Server 2010 environment 1 day 1/27/16 8:00 1/27/16 17:00 3 Server Engineer, Server Administrator.
5. Plan to upgrade customizations 1 day 1/28/16 8:00 1/28/16 17:00 Create an upgrade communications plan 1 day 1/29/16 8:00 1/29/16 17:00 5 Project Manager. 7. Prepare your environment for upgrade 4 days 2/1/16 8:00 2/4/16 17:00 1 Server Administrator. Deploy your Project Server 2016 destination environment 1 day 2/1/16 8:00 2/1/16 17:00 Server Engineer. 9. Prepare your Windows PowerShell environment 1 day 2/2/16 8:00 2/2/16 17:00 8 Server Engineer.
10. Disable backward compatibility mode in your Project Server 2010 environment 1 day 2/3/16 8:00 2/3/16 17:00 9 Server Administrator. 11. Check your Project Server 2010 data for issues that can cause the upgrade to fail 1 day 2/4/16 8:00 2/4/16 17:00 Server Administrator. 12. Create backup copies of your Project Server 2010 farm databases 1 day 2/5/16 8:00 2/5/16 17:00 7 Server Administrator. Restore your Project Server 2010 farm databases for upgrade 1 day 2/8/16 8:00 2/8/16 17:00 Server Administrator.
Upgrade your databases and Project Web App site collections 14 days 2/9/16 8:00 2/26/16 17:00 Server Administrator. SharePoint upgrade 6 days 2/9/16 8:00 2/16/16 17:00 Check the SharePoint content database for errors that can cause upgrade to fail 1 day 2/9/16 8:00 2/9/16 17:00 Attach and upgrade the SharePoint content database 1 day 2/10/16 8:00 2/10/16 17:00 Server Administrator.
18. Add your account as a secondary owner of the Project Web App site collection that you want to upgrade 1 day 2/11/16 8:00 2/11/16 17:00 Server Administrator. 19. Migrate users who are using Windows Classic authentication mode to claims based authentication (optional) 1 day 2/12/16 8:00 2/12/16 17:00 Server Administrator. 20. Check your Project Web App site collection for issues that can cause upgrade of the site to fail 1 day 2/15/16 8:00 2/15/16 17:00 Server Administrator.
21. Upgrade the Project Web App site from SharePoint 2010 mode 1 day 2/16/16 8:00 2/16/16 17:00 Server Administrator. 22. Project Server upgrade 8 days 2/17/16 8:00 2/26/16 17:00 Consolidate your Project Server 2010 databases to a Project Services database 1 day 2/17/16 8:00 2/17/16 17:00. Attach the Project Services database to the web application 1 day 2/18/16 8:00 2/18/16 17:00 Server Administrator.
25. Check your Project Services database for errors that can cause upgrade to fail 1 day 2/19/16 8:00 2/19/16 17:00 Server Administrator. 26. Upgrade the Project Services database 1 day 2/22/16 8:00 2/22/16 17:00 Server Administrator. 27. Mount the Project Web App instance 1 day 2/23/16 8:00 2/23/16 17:00 Server Administrator.
28. Check the Project Web App instance for issues that can cause upgrade to fail 1 day 2/24/16 8:00 2/24/16 17:00 Server Administrator. 29. Upgrade the Project Web App instance 1 day 2/25/16 8:00 2/25/16 17:00 Server Administrator. 30. Enable Project Web App features 1 day 2/26/16 8:00 2/26/16 17:00 Server Administrator.
31. Testing 2 days 2/29/16 8:00 3/1/16 17:00 Test Sharepoint Server 1 day 2/29/16 8:00 2/29/16 17:00 Server Administrator, Server Engineer 33. Test Project Server 1 day 3/1/16 8:00 3/1/16 17:00 Server Administrator, Server Engineer.
Paper For Above Instructions
The following paper discusses the task management for a mobile application project and a Project Server upgrade. Project management involves the rigorous organization and planning of tasks to ensure each milestone is met efficiently.
Mobile App Project Overview
The overall objective for the mobile application project is to complete its development within a defined timeline of 34 days. The project includes several key tasks grouped into sprints. The first sprint focuses on UI development, with design, build, and testing phases introduced into the plan. With the project manager and product owner overseeing the essential components, the development cycle will follow agile principles.
Key Phases and Tasks
The first phase, involving project setup, occurs from February 1-9, 2016. During this time, the project manager collaborates with the product owner to define project processes and set the working environment. The primary goals include determining the initial sprint velocity to measure productivity and identifying initial user stories for subsequent sprints.
Subsequent sprints are categorized based on functionalities. For instance, the first sprint includes user interface design, building the interface, and performing user acceptance testing (UAT). Each of these phases allocates specific days to ensure completion within deadlines. After successfully completing UAT and addressing any issues prompted during testing, the project transitions into Sprint 2, focused on generating specified reports and advancing platform capabilities in Sprint 3.
Project Server 2016 Upgrade Overview
The Project Server 2016 upgrade designed as a waterfall model illustrates a different approach towards task management. The timeline from January 25 to February 26, 2016, caters to an outlined task sequence for performing a system upgrade. Each task corresponds with various roles, including server administrators, technical analysts, and project managers.
Sequential Task Management
Starting on January 25, the first task is reviewing system requirements for the upgrade, concluding only five days later with prepared environments for the upgrade. Unlike agile methodologies, the waterfall approach embraces a linear sequence where each task execution depends on the completion of preceding ones.
Throughout the timeline, essential tasks involve creating backup copies, checking databases for errors, and upgrading the Project Web App site collections. By adhering strictly to predefined steps, the project team minimizes risks that could potentially interrupt the upgrade process.
Conclusion
Effective task management enhances the overall progress in both development projects. By recognizing the different methodologies - agile for the mobile app and waterfall for the server upgrade - managers can optimize resources and streamline processes. Analysts recommend leveraging tools for tracking task completion and ensuring clear communication channels within teams. Both practices result in a structured environment that increases productivity and minimizes project risks.
References
- Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
- Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
- Scrum Alliance. (2020). The Scrum Guide. Retrieved from https://www.scrumguides.org/scrum-guide.html
- PMI. (2016). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Project Management Institute.
- Highsmith, J. (2013). Agile Project Management: Creating Innovative Products. Addison-Wesley.
- Schmidt, C. (2016). Project Server 2016: A Guide for Management and Users. IT Governance Publishing.
- Atlassian. (2021). Agile Coach. Retrieved from https://www.atlassian.com/agile
- Gray, C., & Larson, E. (2017). Project Management: The Managerial Process. McGraw-Hill.
- Wysocki, R. K. (2014). Effective Project Management: Traditional, Agile, Extreme. Wiley.
- Leach, L. P. (2014). Critical Chain Project Management. Artech House.