ICTPRG502 Manage a project using software management

[ad_1]

Assessment Details
Qualification Code/Title ICT50118 Diploma of Information Technology
Assessment Type Assessment – 1 (Written task) Time allowed 2 weeks
Due Date Location SCCM Term / Year

Unit of Competency
National Code/Title ICTPRG502 Manage a project using software management
Student Details
Student Name Student ID
Student Declaration: I declare that the work submitted is my own, and has not been copied or plagiarised from any person or source. Signature:
Date:
Assessor Details
Assessor’s Name
RESULTS (Please Circle) ☐SATISFACTORY
☐NOT SATISFACTORY

Feedback to student:

*If Student is Not Satisfactory
Reassessment Required ☐ Yes ☐ No
Assessor Declaration: I declare that I have conducted a fair, valid, reliable and flexible assessment with this student, and I have provided appropriate feedback.
Signature:
Date:
Comment:
Instructions to the Candidates
 This assessment is to be completed according to the instructions given below in this document.
 Should you not answer the tasks correctly, you will be given feedback on the results and gaps in knowledge. You will be entitled to one (1) resubmit in showing your competence with this unit.
 If you are not sure about any aspect of this assessment, please ask for clarification from your assessor.
 Please refer to the College re-submission and re-sit policy for more information.
 If you have questions and other concerns that may affect your performance in the Assessment, please inform the assessor immediately.
 Please read the Tasks carefully then complete all Tasks.
 To be deemed competent for this unit you must achieve a satisfactory result with tasks of this Assessment along with a satisfactory result for another Assessment.
 This is an Open book assessment which you will do in your own time but complete in the time designated by your assessor. Remember, that it must be your own work and if you use other sources then you must reference these appropriately
 Submitted document must follow the given criteria. Font must be Times New Roman, Font size need to be 12, line spacing should be Single line and Footer of submitted document must include Student ID, Student Name and Page Number. Document must be printed double sided.
 This is Individual Assessments. Once you have completed the assessment, please provide the Hard copy of the Assessments to your Trainer/ Assessor.
 Plagiarism is copying someone else’s work and submitting it as your own. Any Plagiarism will result in a mark of Not Satisfactory.

Assessment Information
The assessment tasks for ICTPRG502 Manage a project using software management are included in this Student Assessment Tasks booklet and outlined in the assessment plan below.
To be assessed as competent for this unit, you must complete all of the assessment tasks satisfactorily

Assessment Plan
Assessment Task Overview
1. Written task Students must correctly answer all questions.
2. Case Study You are required complete the case study based on scenario given in Task.
3. Project work You are required complete the project based on scenario given in Task.
Assessment Preparation
Please read through this assessment thoroughly before beginning any tasks. Ask your assessor for clarification if you have any questions at all.

When you have read, and understood this unit’s assessment tasks, print out the Student Assessment Agreement. Fill it out, sign it, and hand it to your assessor, who will countersign it and then keep it on file.
Keep a copy of all your work, as the work submitted to your assessor will not be returned to you.
Assessment appeals
If you do not agree with an assessment decision, you can make an assessment appeal as per your RTO’s assessment appeals process.
You have the right to appeal the outcome of assessment decisions if they feel they have been dealt with unfairly or have other appropriate grounds for an appeal.
Naming electronic documents
It is important that you name the documents that you create for this Assessment Task in a logical manner.
Each should include:
• Course identification code
• Assessment Task number
• Document title (if appropriate)
• Student name
• Date it was created
For example, ICTPMG401 AT2 Support Small Scale Report Joan Smith 20/10/18
Additional Resources
You will be provided with the following resources before you begin Assessment Task

Assessment Instructions
Each assessment task in this booklet consists of the following:
Assessment Task Cover Sheet
This must be filled out, signed and submitted together with your assessment responses.
If you are submitting a hard copy, the Cover Sheet should be the first page of each task’s submission.
If you are submitting electronically, print out the cover sheet, fill it out and sign it, then scan this and submit the file.
The Assessment Task Cover Sheet will be returned to you with the outcome of the assessment, which will be satisfactory (S) or unsatisfactory (U). If your work has been assessed as being not satisfactory, your assessor will include written feedback in the Assessment Task Cover Sheet giving reasons why. Your assessor will also discuss this verbally with you and provide advice on re-assessment opportunities as per
your RTO’s re-assessment policy.

Depending on the task, this may include
• resubmitting incorrect answers to questions (such as short answer questions and case studies)
• resubmitting part or all a project, depending on how the error impacts on the total outcome of the task
• redoing a roleplay after being provided with appropriate feedback about your performance
• being observed a second (or third time) undertaking any tasks/activities that were not satisfactorily completed the first time, after being provided with appropriate feedback.
Assessment Task Information
This gives you:
• a summary of the assessment task
• information on the resources to be used
• submission requirements
• re-submission opportunities if required
Assessment Task Instructions
These give questions to answer or tasks which are to be completed.
Your answers need to be typed up using the software as indicated in the Assessment Task Instructions.

Copy and paste each task’s instructions into a new document and use this as the basis for your assessment task submission. Include this document’s header and footer.

If you are submitting electronically, give the document a file name that includes the unit identification number, the task number, your name and the date.
Checklist
This will be used by your assessor to mark your assessment. Read through this as part of your preparation before beginning the assessment task. It will give you a good idea of what your assessor will be looking for when marking your responses.

ASSESSMENT 1 – Project
This information is to be handed to each student to outline the assessment requirements
Task summary
You are required to analyse the scenario of SCCM. Based on the given information you are required to design the proposed IT infrastructure for SCCM.

This assessment is to be completed in the simulated work environment in the RTO.
Timing
Your assessor will advise you of the due date of these submissions.
Submit
Project report
Written task
Project Sign off Sheet Assessment criteria
For your performance to be deemed satisfactory in this assessment task, you must satisfactorily address all of the assessment criteria. If part of this task is not satisfactorily completed, you will be asked to complete further assessment to demonstrate competence.
Re-submission opportunities
You will be provided with feedback on their performance by the Assessor. The feedback will indicate if you have satisfactorily addressed the requirements of each part of this task.

If any parts of the task are not satisfactorily completed, the assessor will explain why, and provide you written feedback along with guidance on what you must undertake to demonstrate satisfactory performance. Re-assessment attempt(s) will be arranged later and date.

You have the right to appeal the outcome of assessment decisions if you feel that you have been dealt with unfairly or have other appropriate grounds for an appeal.

You are encouraged to consult with the assessor prior to attempting this task if you do not understand any part of this task or if you have any learning issues or needs that may hinder you when attempting any part of the assessment.

Assessment 01- Written Test

The Assessment Task is due on the date specified by your trainer. Any variations to this arrangement must be approved in writing by your trainer.

Part A: Short Questions (Attempts all question)

The space for the answers are also indicative but does NOT indicate the length of answer. Use as much space as you need to answer the question.

Q1. What is project management? What does manage a project includes?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q2. List four project management tools that could be used to assist in project management.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q3. List and briefly explain four different software development methodologies with their advantages and disadvantages?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q4. What is a successful project? Briefly describe the steps of the software development life cycle (SDLC) with key features?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q5. What is the best way to set up and manage an inter-departmental team? What are the software you can use to manage collaboration in an inter-departmental team?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q6. What is source or version control? Identify and explain different methods.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q7. A software company has 100 developers working from five different countries. Should they use version control tools? What are benefits of using such tools?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q8. What is critical path? What are the advantages of Work Breakdown structure?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q9. What is a project plan and what does a typical project plan include?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q10. In a software project, what type of contingency planning do you do? How do you monitor and manage risks to the project?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Q11. Explain the basic principles of project management.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

12. Write a short note on:
• Microsoft Project
• Microsoft Visio

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Comments
Assessment Method: WRITTEN TEST
Result
(Please Circle) ☐Satisfactory
☐Not Satisfactory
☐Incomplete

Assessor: I declare that I have conducted a fair, valid, reliable and flexible assessment with this student, and I have provided appropriate feedback Name: ___ ______
Signature: ________________________
Date: ____/_____/_____

Assessment Details
Qualification Code/Title ICT50118 Diploma of Information Technology
Assessment Type Assessment – 2 (Case Study) Time allowed Two weeks
Due Date Location SCCM Term / Year

Feedback to student:

If Student is Not Satisfactory
Reassessment Required ☐ Yes ☐ No
Assessor Declaration: I declare that I have conducted a fair, valid, reliable, and flexible assessment with this student, and I have provided appropriate feedback.
Signature:
Date:
Comment:
Instructions to the Candidates
 This assessment is to be completed according to the instructions given below in this document.
 Should you not answer the tasks correctly, you will be given feedback on the results and gaps in knowledge. You will be entitled to one (1) resubmit in showing your competence with this unit.
 If you are not sure about any aspect of this assessment, please ask for clarification from your assessor.
 Please refer to the College re-submission and re-sit policy for more information.
 If you have questions and other concerns that may affect your performance in the Assessment, please inform the assessor immediately.
 Please read the Tasks carefully, then complete all Tasks.
 To be deemed competent for this unit, you must achieve a satisfactory result with tasks of this Assessment along with a satisfactory result for another Assessment.
 This is an Open book assessment which you will do in your own time but complete in the time designated by your assessor. Remember, that it must be your own work, and if you use other sources then you must reference these appropriately
 Submitted document must follow the given criteria. The font must be Times New Roman, Font size needs to be 12, line spacing should be Single line, and Footer of the submitted document must include Student ID, Student Name and Page Number. The document must be printed double-sided.
 This is Individual Assessments. Once you have completed the assessment, please provide the Hard copy of the Assessments to your Trainer/ Assessor.
 Plagiarism is copying someone else’s work and submitting it as your own. Any Plagiarism will result in a mark of Not Satisfactory.
Assessment Information
The assessment tasks for ICTPRG502 Manage a project using software management are included in this Student Assessment Tasks booklet and outlined in the assessment plan below.
To be assessed as competent for this unit, you must complete all of the assessment tasks satisfactorily

Assessment Plan
Assessment Task Overview
1. Written task Students must correctly answer all questions.
2. Case Study You are required to complete the case study based on the scenario given in Task.
3. Project work You need to complete the project based on the scenario given in Task.
Assessment Preparation
Please read through this assessment thoroughly before beginning any tasks. Ask your assessor for clarification if you have any questions at all.

Assessment Instructions
Each assessment task in this booklet consists of the following:
Assessment Task Cover Sheet
This must be filled out, signed, and submitted together with your assessment responses.
If you are submitting a hard copy, the Cover Sheet should be the first page of each task’s submission.
If you are submitting electronically, print out the cover sheet, fill it out and sign it, then scan this and submit the file.
The Assessment Task Cover Sheet will be returned to you with the outcome of the assessment, which will be satisfactory (S) or unsatisfactory (U). If your work has been assessed as being not satisfactory, your assessor will include written feedback in the Assessment Task Cover Sheet, giving reasons why. Your assessor will also discuss this verbally with you and provide advice on re-assessment opportunities as per
your RTO’s re-assessment policy.

Copy and paste each task’s instructions into a new document and use this as the basis for your assessment task submission. Include this document’s header and footer.

ASSESSMENT 2 – Case Study
This information is to be handed to each student to outline the assessment requirements
Task summary
You are required to analyze the scenario of SCCM. Based on the given information, you are required to design the proposed IT infrastructure for SCCM.

You have the right to appeal the outcome of assessment decisions if you feel that you have been dealt with unfairly or have other appropriate grounds for an appeal.

Assessment 02- Case Study

1.0 Description
Shrine Software organisation develops several human resource management software systems that are widely used throughout fortune 1000 companies. Like the popular software companies, this organisation firmly entrenched culture of using the waterfall development method to develop their software products for over 20 years. The organisation consists of nearly 600 engineers/developers involved in developing its products operating in several different locations.
Shrine development organisation develops products consisting of nearly 25 applications that include software for HR, payroll, timekeeping, accounts, and others. Much of the product development uses the PHP programming language, followed by .net. Shrine undertook the agile development transition beginning in 2005 for the engineering team.

1.1 Why Agile?
The first step towards adopting an agile development process came from the senior executive level of the organisation, Chief Technical Officer (CTO). From this perspective, the current development process “didn’t feel right.” While the organisation was not broken going into the agile development transition, CTO’s driving concern was to ensure that as the organisation grew they would not fall into the trap that some other large organizations encounter slowing productivity as opposed to the nimbleness that small teams possess.

Factors contributing to the feeling were the high number of problem reports, time spent debugging the code was increasing at the cost of implementing fewer features the target release date for recent versions of the product slipped, and employee burnout was being experienced. The 12-month product development cycle plan consisted of roughly six months of coding and six months of testing. The plan typically resulted in five months of coding and seven months of testing.

The goals of adopting agile development practices were:
The lower overhead associated with the development
change responsiveness to customer needs
improve the quality of the products
Due to employee burnout, fun was also a reason for adopting agile software development practices. The management team understood that developers wanted to write code. They wanted to create new technology and solve problems. Fixing bugs and regression testing was considered less fun but was a significant piece of the development effort.

For a twelve months’ cycle, developers were spending:
Five months were high-pressure times, due to the unpredictability of testing and debugging.
In seven months, long hours were spent finding and addressing the bugs.

A more sustainable pace was needed, not ‘bug bashes’ where people would stay late to fix bugs within the products. Management wanted to change the cycle from 5/7 to 11/1, where eleven months were spent doing the fun stuff.

This coincides with statements made by Pete Deemer, Chief Product Officer at Yahoo! (India Research and Development):

1.2 Details about the agile implementation
The first steps for adopting agile development methods were initiated by the CTO by having consultants come in and evaluate the organisation. After the consultants observed the organisation development practices, the CTO then presented the results to the organisation and laid out how the development transition would be made. The presentation also showed the engineering team why the change was necessary and how things would improve. This executive level support enabled easy buy-in by the engineering team, as it came from the CTO himself.

A rallying cry of “11/1” was used to motivate employees to see the positive aspects of agile development. “11/1” indicated that the engineering organisation was going to focus much more on the actual development work (11 months), and less time on the integration and final testing phase (1 month). Not only would the change help the company and direct stakeholders, but it would also help the employees by focusing on what engineers want to do, as opposed to the more mundane aspects that were occupying increasing amounts of time.

Five full-time consultants were brought on board, and a team of five to ten internal full-time agile coaches was assembled to provide training to the organization. It took about three months to roll out agile development practices to the organisation. After six months, the consultants left, leaving the internal coaches to finish carrying out the agile transition.

The method took place in two phases. The first phase instituted in 2005 focussed on adjusting the development practices used. These practises include the incremental approach to developing the products in smaller, “bite-size chunks” and retrospective. The second phase, instituted in 2007 involved the adoption of Scrum practices within the organization. This phase introduced role changes for managers and provided greater empowerment to the development teams.

Although Shrine was a traditional waterfall development-based company, there were some practices that the organization had used were agile-based (without using the agile name) that made the choice of choosing agile development easier.

It was decided that the entire suite of products would make the transition to agile development together. This was due to the overhead penalty that was forecast by transitioning one or a few groups and then having to apply an agile transition process to the remaining groups later. Further, it just made sense to transition all teams at once, since there were several products that became integrated into one large suite of application. In the words of one director of development, they were entering uncharted territory, transitioning the whole development organization at once, contradicting recommendations in agile development articles and consultants’ suggestions.
Version control
The Shrine does not have any version control tools at the place. Since multiple developers and personnel from various departments work on a project at one time, now it is difficult to ascertain who has made the changes. Sometimes the changes made by one developer is being overwritten by other developers since they are working on the different versions of the file. They usually have access to the latest version of the code only and do not maintain an older version of the project files and codes now. The backup process is manual, and there is not any definite timeframe for each backup. So, to eradicate these problems, Shrine is planning to implement some version control mechanism for their development task.

1.3 Assessment of the transition
To gauge the progress of the agile transition, coaches are involved in checking the pulse of the teams. They meet every two weeks to discuss the status of the transition. The subsequent addition of scrum practises made it easier to determine an agile health assessment and will show if and where additional focus is needed. The organisation is looking at the possibility of using quarterly audits to assess the state of agile development.

1.4 Role Changes
Shrine encountered role changes for some of the positions within the organisation.

1.4.1 Project Managers (PM)
During the agile transition, PM positions were eliminated. As part of the agile process, product owner positions were used. Most of the PM became scrum masters but those that didn’t want to change left the company.

1.4.2 Developers
The role of the developers changed from writing code solely for the product to spending half of their time writing test code. The position also required a change in their mindset from a “throwing it over the wall” approach.

1.4.3 Testers (QA)
Testers had the initial notion of “we’ll test it once not more than once. “ This notion also underscores the importance of automation testing, as in the words of one director of development, “ You’ll be running the test a thousand times.”

1.4.4 Managers
Middle managers got squeezed the most from the agile development adoption. The lower teams make the process work, and senior managers make proclamations about what needs to be done. Before adopting agile development, they thought about the product and not much time on how to make engineering better. The middle management group is only accountable for productivity.
Your Tasks:
Task-1: Based on this case above, summarise the status of the current project management and software development methodology at Shrine analysing the current strength and problem.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task 2: Identify the reasons the current development methodology “didn’t feel right.”

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-3: Identify the weakness of the Waterfall Method relevant to the Shrine case that led to change its methodologies.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-4: What are the problems Shrine is facing managing the source-control in its daily operation?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-5: How is the proposed “11/1 concept” (as explained above) different from other development methodologies?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-6: what are the advantages that Shrine may get by using agile methodology?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-7: Describe with explanations and examples, why Shrine should make changes to its current software development methodology?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-8: What difference it would have made if Shrine was currently using different methodology such as RAD? Do you think the change to Agile system would be necessary in that case? Justify.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task 9: Determine how Shrine can use source control to handle problems and conflicts related to the source code of the software. Define the process of such a source-control procedure?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task 10: Recommend some of the collaboration software tools (at least four with a brief description) that Shrine can use to facilitate its current projects? Explain which one would you use in this case with justification.

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-11: What could be some of the costs that Shrine might experience in implementing the Agile Methodology?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Task-12: If you are the Chief Technical Officer (CTO) of Shrine, do you agree with the use of the Agile methodology to manage its project? If not, which methodology do you suggest? Why?

Outcome ☐ Satisfactory
☐ Not Satisfactory

Comment

Comments
Assessment Method: WRITTEN TEST
Result
(Please Circle) ☐Satisfactory
☐Not Satisfactory
☐Incomplete

The post ICTPRG502 Manage a project using software management appeared first on mynursinghomeworks.

[ad_2]

Source link

ICTPRG502 Manage a project using software management

DISCLAIMER:

QUICK LINKS

WE ACCEPT

CONTACT US