draw ‘til you’re soreWelcome to the bog of Jessica Amber. Herein you’ll find my life, whatever Irandom stuff ’m getting up to. It’s usually creative.
Unmaintained since 2019. Please go to www.jessicaamber.com.au This site contains affiliate links.
|
The confirmation came through yesterday, and today I begin my biggest course to date, a Diploma in Web Development offered through OTEN, AKA Open Training and Education Network, AKA Tafe Digital. It's looking much more guided and involved than my previous course through tafeNow. The first unit I am doing is ICTICT509, Gather data to identify business requirements. I've been instructed to go to SkillPoint for learning resources. The first thing is a quiz, testing my prior knowledge. I'm going to write down the information I'm learning as I go, to help it stick in my brain.
Monitoring and Controlling -- Validate scope. Control scope. 2a. When creating mind maps for a diverse group of stakeholders, each person can make their own map, and then all these can be consolidated into one map. The instructor should explain that similar ideas should be grouped, and major branches are general while minor branches are more specific 2b. When people are brainstorming together, they should be encouraged to build upon eachother's ideas rather than just focusing on their own 2c. Project requirements can be ranked using the Nominal Group Technique. The steps for which are as follows: a. Place the full list of requirements generated so far in front of the group b. Ask each person to record their top 4 requirements and assign each a number from 4 to 1, with 4 indicating the greatest importance c. Ask each person to read out their top requirements and scores, and write down the results d. Tally the total scores for each listed requirements 3. The purposes of a project scope statement are as follows: a. To guide the focus of work of the project team b. To set the expectations of stakeholders c. To define and progressively elaborate on the work of a project d. To provide a baseline for evaluating whether change requests fall within the project's boundaries The scope statement is NOT a guide for managing project quality, and it does not protect a project from any scope changes. 4. There are several facts about collecting project requirements.
5. When you undergo the Collect Requirements process of a project, you'll be creating two outputs. One is the Requirements Traceability Matrix, and the other is the Requirements Documentation. The Requirements Traceability Matrix will contain the current status of each requirements, and a map relating each requirement to project scope and actual product development as a project is undertaken. The Requirements document will contain requirements, arranged by stakeholder and priority, and a list of assumptions and constraints for each requirement. 6. Scope creep is when extra requirements are added to a project later in the development, without consideration of the impact on budget, time, staff ect. Two examples of scope creep are:
7. In a scenario of making a website for ESL students, there would be many requirements. Some examples of which include:
8. A good description of project scope would be, the boundary around the work required to completed the project deliverables. 9a. If you are collecting requirements, there are several tools and techniques you could use.
10.. If we were making scope management and requirements management plans for a goal of assisting underprivileged children in my hometown, there would be several elements to include:
11. The process Plan Scope Management has several inputs. These include:
12. The process Define scope has several techniques. They are:
13. A project scope statement has several components, including:
14. The process Define Scope has its own inputs. These include:
Well, that's the quiz done. It took me about an hour and a half to complete. My final score as a percentage was 77%, which is better than I expected, considering even the first question had me like "What the heck?" According to a bar chart on the results page, I need 80% on each of the three chapters to pass. So I'm very close. An Overview of Project Scope Management Scope refers to ALL the work required to complete the project's deliverables. If a client's requirements change later on in the project, that is NOT an example of having undefined boundaries. A project's scope contains the product's scope. Scope creep is unmanaged changes to a project's scope. Here are some examples of scope creep:
Some situations that could lead to scope creep include:
That's all for today
xx Jess
0 Comments
Leave a Reply. |
AuthorI'm just some Aussie 20-something year old with a lot of time and a lot of interests. Archives
July 2019
CategoriesAll Art Art Freelancing Business Cosplay Food Law Of Attraction Makeup Organizing Sewing Shopping TAFE Technology Web |