Data and Information Management.
Part 1: MUST BE 2 PARAGRAPHS EACH REPLY 1REPLY TO: * Source code management provides an environment in which multiple programmers can separately but simultaneously develop and test code prior to submitting it to a project, regardless of the geographic location of each participating programmer. This ensures a seamless flow of visible changes as opposed to suspended project development resulting from delays caused by file locking and incompatible contributions; and allowing testing before submission reduces errors in code. Because all programmers contributing to the project know the end goal, and the general design of the project, if something is wrong or missing, different project members can either fix it or bring it to the attention of the programmer assigned to the area of concern; further increasing precision and speed of project development. This community approach to quality assurance encourages effectual communication, creativity and timely completion. Finally, source code management offers flexibility when developing on more than one platform because “by understanding the conventions of the platform, the SCM system can automatically translate between the required formats.” (Smith, 2010) Because SCM systems resolve the disparities between line-ending conventions across platforms, range of development is not limited to one or few platforms, reducing the chance of failure and loss of valuable time in the development process. Smith, Tony (2010, March 1). Protecting the Process. Engineering & Technology,Page 53. Retrieved from https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Feandt.theiet.org%2Fcontent%2Farticles%2F2010%2F03%2Fsource-code-management-protecting-the-process%2F&data=02%7C01%7C%7C4ca1a2480c364d8e6e9008d670b4373b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636820316651820807&sdata=4Vhi8W5M0wqzDQiUQKB0R%2FjntZWUr8xRS1iWQgj0SHk%3D&reserved=0 2REPLY TO: * The management of code in a project is vital and in our current year utilizing a source code management system is almost a professional courtesy. The functions mentioned in Tony Smith’s article “Protecting the Process” sound invaluable when working in a group or good for a to have when working alone. More than likely everyone will be working in a team on a project at some point in the future and will need a way to communicate and compartmentalize the different work. From the article, the SCM systems in use are practical and necessary, giving programmers and designers the ability to easily merge source codes with updates and to patch together entire projects automatically, only needing human intervention if conflicts occur when rewriting. Additionally, SCM system allows for code to be rolled forward and backward when necessary when dealing sync issues with updates coming from different parts of the world when people are working opposite schedules. Another interesting aspect mentioned in the article refers to the software’s ability to identify “ugly code” and prevent it from propagating into future updates, replacing it with better “clean code”. Finally, one of the best functions I read about in this article was the open source, cross-platform development. Working between operating systems is a chore that most people don’t want to tackle and deal with this obstacle often by creating software exclusive to one system. With the ability to easily share information between different platforms it makes programer’s jobs easier. With all these functions it’s practical and necessary for groups or individuals to employ some form of source code management in the projects to work more effectively. Project Management-Part 2: MUST BE 2 PARAGRAPHS EACH REPLY 1REPLY TO: * Project charters typically appoint the project to lead the project. Commonly, project manager transitioning either for new opportunity internal or external of the company or relieved from the project, mechanisms are in place to maintain continuity within the project. According to Andrew Makar, he mentioned tips that are used in an organization to ensure a smooth transition between the out-going and incoming PM’s. 1. Review the project kick presentation. Communication must be made available that articulate project goals, objectives, scope, timeline and major deliverables. 2. Provide a project schedule deep dive. An outgoing Project manager should provide a detailed overview of the project schedule-he/she needs to understand the critical path, key milestones, and core sections of the project. 3. Review the financial management process. Understanding all the processes relative to the forecasts and invoices 4. Share the unspoken truths and the story Communicate an overview of different personalities from the project team, stakeholders and the overall project. 5. Provide an overview of the project stakeholders and their interests. As mentioned above of the different personalities of stakeholders, each one may have a different requirement like some members want recurring updates more frequently than others-the oncoming PM would need to understand and prioritize each member. 6. Agree to be available by phone for two weeks Outgoing PM’s are encouraged to be available after leaving the company in case any questions may come about concerning the project. https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.techrepublic.com%2Fblog%2Fit-consultant%2Fsix-tips-for-a-successful-project-manager-transition%2F&data=02%7C01%7C%7C4ca1a2480c364d8e6e9008d670b4373b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636820316651820807&sdata=26EO9jHLpZIcWSEwwoiAkN4W2qDAacUU2v3TdVh%2BNnk%3D&reserved=0