Team member: Project:Date:
Performance Review
Team member: Project:Date:
Metrics:
1: ___________________________________
2: ___________________________________
3. ___________________________________
4. ___________________________________
Overall performance
Rate the employees general performance in relation to their continuous improvement efforts
Metric Outstanding Good Acceptable Unacceptable
1 2 3 4 IMPROVEMENT OPPOrtunities
Strengths Improvements required Training needs
RTO No: 91223
-5406891432060
Student Project Portfolio
ICTSAD609 Plan and monitor business analysis activities in an ICT environment
CONTENTS
TOC o "1-3" h z t "RTO Works Heading 1,1" Section 1: Establish business analysis approach PAGEREF _Toc54860931 h 5Section 2: Plan business analysis activities and communication PAGEREF _Toc54860932 h 8Section 3: Manage business analysis PAGEREF _Toc54860933 h 12
Student name: Assessor: Date: Business this assessment is based on: Business analysis initiative 1: Business analysis initiative 2: Numeric and Financial data:
Section 1: Establish business analysis approachProvide business overviewProvide an overview of the business, including:
name of business
description of what the business does. Describe business analysis initiativesDescribe the two selected ICT business analysis initiatives associated with the business. Include:
a brief outline of each initiative, including:
the type of ICT project
a description of the initiative
an explanation of how each initiative supports the organisations vision and strategyan appropriate business analysis tool to illustrate and fully define the initiative (e.g. SWAT analysis)
two objectives of each initiative. Legislative and organisational requirements
Establish the legislative and organisational requirements related to each complex issue, including:
a summary of the relevant legislation
a summary of applicable standards
a summary of the associated organisational policies and procedures
Attach any relevant policies to your portfolio. Identify stakeholdersProduce a complete list of everyone involved in, affected by or responsible for each initiative. In your answer:
use an appropriate business analysis technique (e.g. affinity diagrams) to identify all stakeholders
establish a list of internal and external key stakeholders, including:
the use of an appropriate technique (e.g. power/interest grid)
who they are and how they relate to the initiativewhich stakeholders have authority over business analysis activitiesexplain how you will identify and deal with new stakeholders throughout the duration of each initiative. Establish process needsUse standards and policies/procedures to establish organisational process needs applicable to each business analysis initiative, including:
Relevant personnel
Engagement with personnel to obtain information on how work will be completed (e.g. draft email and minutes of meeting)
A description of an appropriate project management method or tool to support the business analysis initiative.
Attach proof of engagement with staff to your portfolio. Plan execution of activities
Plan the execution of business analysis activities according to organisational requirements for each initiative.
61859414351000 Attach: Organisational policies and procedures
Legislation
Standards
Proof of engagement with staff
Section 2: Plan business analysis activities and communicationSummarise the outcomes of the stakeholder meetingsSummarise the meetings with key stakeholders for each initiative, including:
stakeholder attitudes towards the initiative
at least two risks associated with the stakeholdersdecide how to best mitigate the identified riskat least three business analysis deliverables, including:
the deliverable
tasks/activities associated with the deliverablethe use of a technique/tool to outline the activities performed by the business analyst and when (e.g. project schedule)
stakeholder requirements, including:
list of requirements
explanation of the tool or technique used to illicit requirementsAttach proof of the technique used during the meeting to illicit requirements. Determine business analysis scopeScope business analysis activities for each initiative, considering:
deliverables and activities approved at the stakeholder meetingacceptance criteria, level of detail, level of formality and frequency
how risks identified in Section 1 can be mitigated
how to address competing demands. Develop estimates for business analysis workUse an appropriate technique to estimate business analysis work, including the use of numeric and financial information and mathematical calculations.
Plan internal and external stakeholder communication for each initiative, considering for each stakeholder:
how to:
receive information
distribute information
access information
update informationescalate informationCommunication constraints (list at least two) Plan business analysis performance management
Plan business analysis performance. Include:
at least three metrics to measure work performed by business analystreporting format. Develop a requirements management process.
Develop a requirements management process by establishing a requirements repository, including:
Description of the repository
Attributes to be capturedOutline of the need and process for traceability considering applicable factorsRequirements change process Prepare for stakeholder meetingPrepare for the stakeholder meetings (e.g. by updating the project schedules).
Attach proof. Prepare for business analyst meetingEvaluate the business analysts performance against pre-determined metrics and identify any problems or areas of improvement. Use the format determined previously in this section.
If applicable, use the Performance Evaluation Template.
Attach proof. 61859414351000 Attach: Proof of requirements tool/technique used in stakeholder meeting
Preparation for stakeholder meeting (e.g. project schedule)
Business analyst performance evaluation
Section 3: Manage business analysis
Summarise the outcomes of the stakeholder meetingsSummarise the meetings with stakeholders, including:
any changed positions or requirements the stakeholders may haveidentify any new stakeholdersExplain how the changed positions/requirements will be managed. Summarise business analyst meetingSummarise what was discussed at the business analyst performance management meeting. In you answer include:
A summary of the discussion
Corrective actions required Confirm recommendations
Confirm the recommendations made during the performance management evaluation using an appropriate communication channel (e.g. updated project schedule, email).
Attach proof. Problem solving
Explain how you managed problem solving for business analysis activities drawing on your existing experience.
61859414351000 Attach: Proof of confirmation of performance evaluation recommendation
RTO No: 91223
-5406891432060
Student Guide
ICTSAD609 Plan and monitor business analysis activities in an ICT environment
CONTENTS
TOC h z t "RTO Works Heading 1,1" Overview PAGEREF _Toc55383598 h 4Topic 1: Business analysis within an organisation PAGEREF _Toc55383599 h 5Topic 2: Business analysis approach PAGEREF _Toc55383600 h 10Topic 3: General business analysis planning PAGEREF _Toc55383601 h 16Topic 4: Detailed business analysis planning PAGEREF _Toc55383602 h 21
Overview
Application of the unit
This unit describes the skills and knowledge required to establish and manage Information and Communications Technology (ICT) business analysis activities in a medium-to-large organisation.
This unit applies to individuals who require high-level management, business and technical skills to manage complex analysis efforts within the Information and Communications Technology (ICT) industry, often as part of business-critical ICT projects.
No licensing, legislative or certification requirements apply to this unit at the time of publication.
Learning goals
Learning goals include:
understanding business analysis within an organisation including project management and business analysis processes
planning a business analysis approach for an ICT initiative
planning general business analysis activities, including deliverables and performance management
detailed planning for business analysis activities, including stakeholder management, requirements management and change management.
Topic 1: Business analysis within an organisation
The list of innovative concepts that have changed life as we know it is endless internet, space travel, smartphone and on demand television are only a few. While some ICT innovations are a response to needs or problems, many ICT products, services, processes and programs have emerged from opportunities and gaps in the marketspace.
Business analysis supports ICT initiatives to fully identify and address complex needs, opportunities or problems in an organisation.
Overview of business analysis
Before we continue, its helpful to define business analysis within an ICT environment.
Activity: Read
Read the article outlining the role and responsibilities of an ICT business analyst.
Article: https://jobdescriptionandresumeexamples.com/ict-business-analyst-job-description-example-duties-and-responsibilities/
Take notes and keep them for future reference.
Activity: Research and discus
Use the article youve just read to answer the questions below (if required, do additional research):
define the term business analysis
explain what business analysts do (particularly in an ICT environment)
list at least three different job titles business analysis practitioners may have
establish the value of business analysis to an organisation.
Your trainer will facilitate a group discussion to consolidate your findings.
From your research, you will have established that business analysts use data to outline problems, needs or opportunities in an organisation or marketspace and monitor and support initiatives to address them.
Business analysis aims to maximise stakeholder benefit by meeting the requirements of both clients and company management.
Business analysis within a bigger picture
Recently, there has been a shift in business analysis from being task driven (e.g. improve an existing process) to value driven (e.g. prioritise new opportunities and improve customer understanding).
Research shows that organisational leaders are now looking for help to navigate the increasing complex business world with timely business analysis insights to assist with decision-making. As such, business analysis should always align to an organisations vision and strategy.
Activity: Discuss
Mailchimp, Airbnb, Uber and Wave are examples of businesses that identified and used ICT opportunities successfully.
In a group, discuss the link between vision, strategy and business analysis in the success of these ventures.
Image by Startup Stock Photos on Pexels
Business analysis and project management
Key to any successful project (including a business analysis initiative) is project management. Project management is necessary for the entire duration of business analysis activities.
Activity: Read and discuss
Read the article explaining project management.
Article: https://www.pmi.org/about/learn-about-pmi/what-is-project-management
In a group, discuss the general project management process.
Keep these steps in mind as you work through this course. Take notes and keep them for future reference.
Choosing the right approach to managing a project plays an important role in its successful delivery.
The method you choose for the project management of business analysis and any related business analysis initiatives depends on:
the organisational requirements
the initiatives complexity
teams involved.
06871970Table 1: Project management methods
0Table 1: Project management methods
The table below outlines a few project management methods.
Method Description
Classic This is technique ideal for small teams and simple projects that includes preparing a plan of upcoming work, estimating the tasks, allocating resources, providing and receiving feedback from the team and monitoring quality and deadlines.
Waterfall This method builds on the classic method and is suitable for more complex projects. It focuses on the sequential performance of tasks. Gantt charts are often used.
Agile project management This method is a value-centred approach based on a set of principles. It is used in software development projects that involve frequent iterations. The team involved is usually small and highly collaborative. Work is divided into short sprints and planning is often adapted and improved. Agile frameworks may include techniques such as Scrum and Kanban.
Rational unified process (RUP) This method is a framework designed for software development teams where end-user satisfaction is the key requirement. It focuses on an iterative development process where feedback forms an integral part of the project.
Program evaluation and review technique (PERT) This method is widely used across many areas and is particularly suitable for large, long-term project with non-routine tasks. It uses detailed planning with a focus on the analysis of tasks performed. Work is represented using PERT charts.
Critical path / Critical chain technique Critical path is an algorithm used together with PERT for scheduling and planning projects where deadlines are critical. It involves detecting the longest sequence of tasks and then defining critical tasks (those that influence the end date).
Critical chain is similar to critical path, except its less rigid and provides more flexibility in resource allocation. It prioritises time allocation.
Extreme project management (XPM) This method emphasises elasticity in planning and is ideal for large and uncertain projects. It is an open, less formal approach that focuses on the human aspect in project management.
040005Table 1: Project management approaches
0Table 1: Project management approaches
Activity: Research and discuss
Work in small groups. Research one tool outlined in table 1 (except the classic method) and present your findings to a larger group.
In your presentation, include:
a description of the method/technique
tools that support the method
a diagram to illustrate the method
advantages and disadvantages of the method
Present you research to a larger group and share your presentation (e.g. via email or a link to a cloud-based storage location) with the other groups for future reference.
From your research, you will already have identified tools that support different project management methods/techniques. Nowadays, there are numerous software tools available to help.
Activity: Reflect
Are you familiar with any project management software?
Activity: Explore
Explore the website below to familiarise yourself with the project management software packages available:
Website 1: https://mopinion.com/top-20-best-project-management-software-an-overview/
Website 2: https://www.capterra.com/sem-compare/project-management-software?gclid=EAIaIQobChMIvND5q6Cw7AIVFVZgCh16BA5OEAAYAyAA EgLpOPD_BwE
Business analysis process
Like project management, business analysis follows a systematic process:
orientate the business analysis initiative
plan business analysis requirements related to the initiative
manage business analysis activities
support the implementation of initiative
review business analysis efforts.
Activity: Discuss
In a group, discuss the connection between project management and the business analysis process.
Activity: Reflect
How do you think business analysis can add value to your workplace (past or present) or field of interest?
Topic 2: Business analysis approach
The start of any business analysis initiative stems from either a need, opportunity or problem where the initiative is a response/solution to the need/problem or opportunity.
The approach to business analysis depends on the problem/need/opportunity and the related organisational and legislative requirements.
Identifying business analysis initiatives
Activity: Brainstorm
Work together in small groups and brainstorm:
a list of general business analysis initiatives relevant to an ICT environment
organisational process requirements related to the initiatives.
Your trainer/assessor will facilitate a larger group discussion to create a complete list.
Sometimes the need, opportunity or problem is obvious and other times analysis is required to identify and fully understand the issue.
Table 2 outlines a few tools that can be used to identify business analysis initiatives.
Tool Description
SWOT analysis This method considers internal factors such as strengths and weaknesses as well as external factors such as threats and opportunities.
S Strength
W Weakness
O Opportunity
T Threats
MOST analysis This method helps analyse what a business does and wants to achieve. It focuses on strategic alignment by understanding an organisations purpose and ability.
M Mission (purpose)
O - Objectives (Key goals that help achieve the mission)
S Strategies (Options to achieve the objectives)
T Tactics (How the strategies will be materialised by action)
Business Process Modelling (BPM) This method focuses on process improvement initiatives. It helps understand the gaps between existing processes and future processes. These processes can be strategic, operational or technical. Processes are represented in a sequential flow using standardised notation.
PESTLE analysis This method identifies external factors that influence business. I
P Political (e.g. government initiatives and support)
E Economic (e.g. labour and energy costs)
S Social (e.g. education and media)
T Technological (e.g. new technology)
L Legal (e.g. regulations)
E Environmental (e.g. weather, pollution, recycling)
CATWOE This method is a generic way to understand what a business is trying to achieve. It helps identify problems and how the solution will impact stakeholders.
C Customers (who are the beneficiaries and how are they affected)
A Actors (who is involved in the situation)
T Transformation (what transformation exists at the heart of the system)
W World view (the big picture)
O Owner (who is the owner of the impacted system?)
E Environmental constraints (how do external factors play a role?)
Root cause analysis This method identifies the root causes of problems and outlines an appropriate preventative response. It is based on the idea that effective management requires more than responding to problems that develop, but finding a way to prevent them.
Brainstorming This is a creative team technique and is used to generate ideas. It may be used with other tools (such as SWOT analysis, root cause analysis etc).
01011Table 2: Business analysis tools for identifying initiatives
0Table 2: Business analysis tools for identifying initiatives
Image by Lukas on Pexels Activity: Research and discuss
Work in small groups. Research one tool outlined in table 1 and present your findings to a larger group.
In your presentation, include:
a description of the tool
a diagram to illustrate the tool
advantages and disadvantages of the tool
an example illustrating the use of the tool.
Present your research to a larger group and share your presentation (e.g. via email or a link to a cloud-based storage location) with the other groups for future reference.
Objectives
Once a business analysis initiative has been identified, its important to establish why it should be pursued.
Well-defined objectives are key to the success of ICT initiatives. They guide activities and decisions throughout the project duration.
When forming objectives, keep the organisations vision and strategy in mind.
Activity: Read
Read the definition of an objective in a business context.
Article: http://www.businessdictionary.com/definition/objective.htmlTake notes for future reference.
Activity: Watch
Watch the videos about objectives.
Video 1: https://www.youtube.com/watch?v=gABgNjXpzQk (01:49)
Video 2: https://www.youtube.com/watch?v=voZI75TyeHI (02:32)
Take notes and keep them for future. Your trainer will facilitate a group discussion to consolidate what youve learnt.
Activity: Group work
Work in small groups: Choose one ICT initiative from the previous brainstorming activity and write at least two objectives for the initiative.
Share your work with another group and ask for feedback. If required, your trainer will provide feedback too.
Organisational and legislative requirements
Standards, legislation and organisational policies/procedures are put in place to make sure everyone is as safe as possible and to ensure a successful outcome for the business or organisation. They also prescribe how things should be done and will influence the approach you choose to follow during business analysis.
Identify any organisational and legislative requirements (including standards, guidelines and processes applicable to the initiative) to ensure compliance and best practise throughout the life cycle of the initiative.
Legislation
Activity: Research
Research legislation associated with your workplace or industry of interest that may be related to an ICT initiative.
You may consider:
Corporations Act
Occupational Health and Safety Acts (industry specific)
Privacy Acts
Chain of responsibility legislation
Employment practises legislation
Copyright legislation
Freedom of Information legislation
Children and Young People legislation.
Take any notes to summarise what you have read and keep them for future reference.
Activity: Discuss
In a group, discuss examples how legislative requirements may differ in different jurisdictions (e.g. Data privacy legislation).
Policies and procedures
Relevant policies and procedures should be considered when defining process requirements for the business analysis initiative. Examples may include employee code of conduct, vendor protocol, social media protocol, document format/naming/storage protocol and performance management.
Activity: Brainstorm
In small groups, brainstorm a few more organisational policies and procedures that may be applicable to an ICT business analysis initiative.
The trainer/assessor will facilitate a group discussion to create a complete list.
Standards
ISO standards are a source of best practice information. They are a set of best practise standards for a range of industries, workplaces and jobs that have been internationally agreed on by experts.
Activity: Explore
Explore the ISO standards website and familiarise yourself with any applicable ICT standards (or any other standards related to your workplace or industry of interest):
Website: https://www.iso.org/standards.html
Take notes and keep them for future reference.
Activity: Explore
In response to the COVID-19 pandemic, the Australian government created an app to facilitate contract tracing. Read the Australian government website link that outlines the COVIDSafe app.
Article: https://www.health.gov.au/resources/apps-and-tools/covidsafe-app
Activity: Practical
Once youve read the article:
identify the need/problem/opportunity of the Australian Department of Health that resulted in the new ICT initiative
explain how the initiative fits into the bigger picture and strategic priorities of the Australian Department of Health
use one business analysis technique (e.g. MOST analysis) to identify and define the opportunity/need/problem (i.e. contract tracing) and associated solution (i.e. the app)
establish the objectives of the initiative.
Assume that prior to developing the COVIDSafe app, business analysis was planned by relevant government officials.
choose an appropriate project management tool management that could have been used to manage the business analysis project (give reasons for your choice)
identify departmental and legislative requirements related to the initiative, including any applicable standards
summarise business analysis requirements related to the development of the app (e.g. communicate with stakeholders, determine specifications etc.)
make a list of potential personnel who may have contributed to work done on the initiative
Compare your work with another student and give each other feedback. Make any necessary adjustments to your work.
If required, your trainer will provide feedback.
Topic 3: General business analysis planning Activity: Reflect
Reflect on what you learnt about business analysis in topic 1, particularly about what a business analyst does and the different job roles a business analyst can fulfil in an ICT environment.
After legislative and organisational requirements have been established and considered, engage with personnel to determine how work will be completed. This topic focuses on the planning related business analysis only.
Deliverables and scope of business analysis activities
All business analysis initiatives have deliverables. The deliverables may be related to the broader initiative, or to specific parts of the project.
Deliverables are established upfront and often associated with a project milestone (think back to what youve learnt about project management).
Examples of business analysis deliverables include:
business analysis plan
stakeholder management plan
requirements management plan
business requirements document
system requirements specification
product backlog
business analysis communication plan.
The Business Analysis Book of Knowledge (BABOK) distinguishes between work products and deliverables. Work products may not necessarily become deliverables, but still form an important role in the business analysis process. According to BABOK:
A work product is a document or collection of notes or diagrams used by the business analyst during the requirements development process.
A deliverable is any unique or verifiable work product or service that a party has agreed to deliver.
For example, as a business analyst establishes the requirements for an ICT initiative, they need to use a variety of techniques to engage with stakeholders to ensure all requirements are identified. As part of this process, a business analyst may informally create mind maps, audio recordings, presentations or notes etc. These may not end up being a deliverable themselves, but may used (and even included) in the Systems Requirements Specification (SRS document) which is a deliverable.
Activity: Group work
Work in small groups. Start a list of business analysis related deliverables. For each deliverable, include the tasks that need to be done for the deliverable to be completed.
For example:
Deliverable Business analysis plan
Tasks Establish objective, assess legislation, define deliverables and scope
Your trainer will facilitate a larger group discussion to create a comprehensive list.
As you progress through the course, add deliverables to this list.
The scope of a business analysis activity defines what the business analyst will do and deliver. This may include deliverables, acceptance criteria, level of detail, level of formality and frequency. Remember its easier and cheaper to correct misaligned expectations during the analysis phase rather than at the end.
Estimates
Once business analysis deliverables have been finalised and the scope has been approved, project management should be used to establish and approve which activities various business analysts will perform and when.
Activity: Discuss
Consider the list of business analysis deliverables you created in the previous activity.
In a group, discuss the timing of different deliverables relative to one another (e.g. business analysis plan is created before the SRS document).
Take notes and keep them for future reference.
Estimates for business analysis work should also be developed. This may include:
internal labour time and costs for tasks and deliverables
external consultancy fees
opportunity costs for not pursuing more value adding activities
travel and accommodation costs for meetings and workshops
04167684Table 3: Estimate methods
0Table 3: Estimate methods
Common estimation methods are outlined in the table below.
Method Description
Top down This method starts with high-level elements which are subsequently broken down into lower levels and then added.
Bottom up This method starts with lower organisation level costs for individual effort and then adds them.
Rough order of magnitude This method provides a high-level estimate and is useful when there is very little information to work with.
Delphi This method uses a combination of expert judgement and historical information to estimate costs and labour requirements.
PERT This method gives each element of the estimate three values:
optimistic value (best-case scenario)
pessimistic value (worst-case scenario)
most likely value (most likely value).
A PERT value for each element is calculated as a weighted average:(Optimistic + Pessimistic + (4 times Most Likely))/6.
Activity: Practical
Work in pairs and practise using financial information, costs and values to determine estimates for business analysis work. Include mathematical calculations (e.g. using the PERT method).
Use your own financial information, or you can access information from:
Website 1: https://www.payscale.com/research/AU/Country=Australia/Salary
Website 2: https://www.abs.gov.au/statistics/economy/price-indexes-and-inflation/consumer-price-index-australia/latest-release
Performance management
Workplaces need timely, accurate and constructive feedback in order to succeed and performance management creates sustainability within an organisation. As you lead and monitor business analysis initiatives, you will most likely provide feedback to the business analysts working on the specific ICT initiative.
Activity: Read
Read the article on how to deliver effective feedback in the workplace.
Article: https://hub.highspeedtraining.co.uk/feedback-in-the-workplace/Take notes and keep them for further reference.
Metrics can be used to measure the work performed by business analysts and may be used to track, assess and report on work quality. If necessary, performance management facilitates corrective action.
To successfully manage business analysis performance, planning according to organisational policies and procedures is essential. When planning for performance management, consider:
performance measures, such as:
deliverable due dates
number of review cycles
frequency of changes to requirements
stakeholder feedback
peer review
performance reporting, including:
formal (written document)
informal (verbal)
preventative and corrective action, considering:
continuous improvement
the impact on the business analysis plan
stakeholder expectations
input from relevant personnel and stakeholders, such as:
Project manager
Tester
Operational support staff
End-user
SME.
Activity: Research and discuss
Research metrics relevant to business analysis. Add metrics to the list of metrics already mentioned in this section.
Compare your list in a small group. Take notes and keep them for future reference.
Activity: Practical
Consider the COVIDSAFE app website you explored at the end of topic 2 (https://www.health.gov.au/resources/apps-and-tools/covidsafe-app) and continue on from the work you did in the previous develop activity to:
identify what type of ICT initiative the COVIDSafe app is
establish deliverables and scope of the business analysis activities that could have been part of the initiative
create a project management schedule outlining which activities business analysts should perform and when
develop estimates for business analysis work
list relevant metrics (at least three) to monitor and assess business analysis work
Compare your work in small groups and give each other feedback.
If required, your trainer will provide feedback.
Activity: Reflect
Reflect on the work youve done so far in the Practical activities:
What did you do well?
What can you improve on?
What actions are required to make the improvements?
Topic 4: Detailed business analysis planningThink back to what you learnt in Topic 3 the deliverables and scope plan the business analysis requirements.
Further planning is required for a successful outcome to the business analysis initiative. This topic addresses a few more project management aspects related to planning business analysis.
Stakeholder analysis
Various stakeholders will be involved right from the beginning of an initiative and a plan is required to successfully manage stakeholder contribution and expectation.
There are many advantages to considering the perspectives of as many stakeholders as possible, such as:
as many opinions and experiences as possible are considered
a full range of requirements are established
the initiative is viewed from different angles
legislation and organisational policies and procedures are adhered to
negative stakeholder reactions can be managed.
Stakeholder management process
A typical stakeholder management process is described in table 4.
Step Description Tools/techniques Documentation
Identify stakeholders In this step, produce a complete list of everyone involved in, affected by or responsible for the initiative.
Stakeholders may be internal (for example, CEO) or external (for example, environmental lobby group).
Consider:
Who could be affected before, during or after the initiative?
Who has an interest in the outcome of the initiative?
Who is responsible for the initiative?
In technology initiatives, subject matter experts (SMEs) are often involved.
Consider how to identify and deal with new stakeholders throughout the duration of the business analysis initiative. Brainstorming:
nominal group technique
Crawford slip method
affinity diagrams
Interviews with known stakeholders
Previous projects lists of stakeholders
Contracts with vendors and suppliers
Social network analysis Stakeholder register
Classify stakeholders Not all stakeholders will have equal influence or interest in the project. Key stakeholders are those stakeholders who have the most influence over the initiative. Separate the identified stakeholders into groups, so that an approach to set and manage their expectations and input can be developed with priority placed on key stakeholders. Establish which stakeholders will have authority over business analysis activities (for example, who will sign off on the functional requirements specifications?). Many times, legislation and organisational policies will determine where authority lies. Salience model
Power/Interest grid Stakeholder analysis
Develop stakeholder management strategy This step includes a confidential document that plans to maximise the influence of stakeholders who support the initiative (and limit any negative effects caused by stakeholders opposed to it). Assess each stakeholders attitude towards and influence over the initiative.
Stakeholders will react in different ways to project actions and by identifying triggers and planning mitigation, you can avoid preventable complaints. Organisational policies and procedures
Legislation (e.g. Natural justice and procedural fairness)
Standards/codes of best practice
Targeted questioning
Risk management Risk register
Stakeholder action plan
Plan communication Plan how to communicate with each stakeholder group. Determine methods to:
Receive (e.g. monitor media, social media, regulatory authorities, email, board meetings, executive team meetings, surveys)
Distribute (e.g. social media, website, email, legal notification, blog, face to face presentation, board papers)
Access (e.g. website links, regulatory portals, internal communications, political briefings)
update (e.g. social media posts, internal meetings, project schedule)
escalate information (according to regulatory requirements and organisational policies and procedures)
Consider communication constraints applicable to different stakeholders. Organisational policies and procedures
Legislation (e.g. Natural justice and procedural fairness)
Standards/codes of best practice
Internet, social media Stakeholder communications plan
Execute communication Distribute information and report performance to manage stakeholder expectations. This may include:
change the stakeholder's expectation to meet the project reality
change the project reality to meet the stakeholder's expectations
change both the stakeholder's expectation and the project reality
-1076325320675Table 4: Stakeholder analysis and management
0Table 4: Stakeholder analysis and management
Organisational policies and procedures
Project management Communication register
Scope
Project schedule
Minutes of meeting
Requirements repository and change management policy
Activity: Read
For further information and examples of stakeholder management documentation, take a look at the article below:
Article: https://www.pmi.org/learning/library/stakeholder-management-plan-6090
Activity: Brainstorm
As part of the Identify stakeholder step in the stakeholder management process, you were reminded to consider identifying new stakeholders throughout the business analysis process.
In a group, brainstorm how to review and identify new stakeholders.
As part of the Plan communication step in the business analysis process, you were reminded to consider communication constraints applicable to different stakeholders.
In a group, brainstorm communication constraints that may impact stakeholders.
Take notes and keep them for future reference.
Risk management
Risk is the chance of something going wrong or not as planned. No outcome is ever one hundred percent certain.
As part of stakeholder management, business analysts aim to minimise the risk of problems occurring during the lifecycle of the initiative due to misaligned stakeholder expectations.
03004396Table 3: Types of business risk
0Table 3: Types of business risk
Planning for risk helps mitigate any undesirable effects. Take a look at the table below to understand more about different types of risks to consider as part of a stakeholder management plan.
Type of risk Description
Strategic risk These risks can occur at any time and are related to the business or organisations strategy.
Compliance risk These risks involve having to comply with rules set by government or regulatory bodies.
Financial risk These risks affect the financial health of a business (cash flow, liquidity, financial position, debt burden etc.)
Operational risk These risks are associated with a business or organisations systems and processes.
Activity: Brainstorm
In a group, brainstorm examples for each type of risk relevant to an ICT environment.
Here are a few tips to help you identify the risks associated with a business analysis initiative:
ask yourself when, where, why and how are risks likely to happen
brainstorm
ask what-if questions
consider worse-case scenarios
use experience how have similar business/organisations experienced risk.
Activity: Discuss
Consider the quote:
Take risks: if you win, you will be happy; if you lose, you will be wise (unknown author).
In a group, discuss this quote.
Do you agree with it?
How is right? How is it wrong?
While some risks can be predicted and managed (particularly internal risks such as safety issues and legal compliance), other risks are less easy to predict and control (particularly external risks such as changes to government regulations). Depending on the risk and its consequences, different actions can be taken to address it (in other words mitigate the risk). These actions are usually one of the following:
avoid the risk (for example, avoid the risk of employees being distracted by not allowing them access to any social media sites during business hours)
prevent the risk (for example, prevent data leakages by limiting the number of people who have access to sensitive information)
contain the risk (for example, contain the risk of hackers accessing data by installing a stronger firewall)
accept the risk (when the risk level is very low, when the treatment cost is much higher than the cost of the damage or when the benefit of taking the risk far outweighs the potential damage)
transfer the risk (for example, seeking legal advice about employee contracts).
Activity: Reflect
Think back to the risk examples you brainstormed previously. For each example, how would you approach mitigation (e.g. avoid, prevent, contain, accept, transfer)?
Requirements analysis
To minimise risk and avoid a mismatch between the end-product (e.g. whats been designed and developed) and what is actually needed, requirements analysis is required.
Requirements
Stakeholders should be consulted when requirements are being established (think back to what you learnt about a stakeholder communication plan). Figure 3 outlines different types of requirements.
17081687338Figure 3: Requirements classification
0Figure 3: Requirements classification
Activity: Discuss
As a group, discuss ICT examples for each requirement category (for example, the code language used during development may be a technical requirement).
Take notes and keep them for future reference.
Different tools and techniques exist that may be used to fully identify requirements. For example:
context diagram
use case diagram
user stories.
Activity: Read
Read the article that explain the above-mentioned tools:
Article 1: https://www.corpedgroup.com/resources/ba/HowShouldBADefineScope.asp
Article 2: https://blog.easyagile.com/how-to-write-good-user-stories-in-agile-software-development-d4b25356b604
Take notes and keep them for future reference.
Technology solution patterns
As you plan requirements (particularly technical requirements), consider technology solution patterns. A technology solution pattern describes a general solution or idea that can be applied to many projects. In an ICT environment, software designers adapt the particular solution pattern to their specific project (they may use more than one pattern).
Activity: Read
Read the blog on ten common software architectural patterns.
Website: https://towardsdatascience.com/10-common-software-architectural-patterns-in-a-nutshell-a0b47a1e9013
Take notes and keep them for future reference.
Activity: Reflect
Have you had any experience with technology solution patterns?
Requirements management
When multiple stakeholders are involved, requirements may contradict or oppose each other. Perhaps stakeholder expectations are unrealistic.
Requirements need to be achievable. For this to happen, they must be prioritised and managed.
A requirements repository stores requirement details (including those under development or review) and supports:
documenting project requirements
versioning requirements
tracing requirements through the analysis and design process
tracking the status of requirements (e.g. via reporting)
managing the requirement change process.
Figure 3 outlines what to consider when documenting and versioning requirements.
17083497186Figure 3: Requirements repository
0Figure 3: Requirements repository
Activity: Brainstorm
In a group, brainstorm how each of the attributes listed above can be used when managing requirements, stakeholders and deliverables.
Take notes and keep them for future reference.
If you think back to topic 1, you will recall that any business analysis effort should align with the organisations strategy. Requirements tracing helps trace requirements all the way back to business objectives.
Requirements tracing allows business analysts and key decision makers to understand why the requirement exists, how to prioritise the requirement and how any changes impact other requirements.
Factors influencing traceability include:
environment (e.g. development of new technologies)
organisation (e.g. corporate strategy commitment to quality system development and continuous improvement)
system development policies (e.g. standard methodology)
stakeholder relationships (e.g. quality of information available).
Requirements management software can be used to manage requirements. Features may include the ability to define requirements, model relationships, reuse requirements, export or import requirements data, graphic tools for visualisation, traceability and real-time impact analysis, collaboration and integration with other tools.
Requirement changes
For all projects, including ICT related initiatives, stakeholders may change their minds (e.g. missed requirements, identified a defect, changed needs, politics, marketplace changes and legislation changes). A change management process should align with the business analysis, project management and communication approach. Adhere to policies and procedures when changes are initiated and make sure the changes are recorded in the requirements repository.
For example:
policies and procedures and business analysis plan may address scope changes
Requirements tracing will assist the business analyst to determine the impact of the change.
communication plan may outline how changes are communicated to stakeholders a
project management approach (e.g. Agile) will prioritise and schedule the change
Activity: Practical
Consider the COVIDSAFE app website you explored at the end of topic 2 (https://www.health.gov.au/resources/apps-and-tools/covidsafe-app) and continue on from the work you did related to the COVIDSafe app in topic 3. Use appropriate tools and techniques to:
perform stakeholder analysis:
identify stakeholders
classify stakeholders
develop a stakeholder management strategy
plan stakeholder communication
plan requirements management:
establish a requirements repository
confirm attributes to be captured
access the need and process for traceability
establish a requirement change management process.
Compare your work in small groups and give each other feedback. If required, your trainer will provide feedback.
Summary
Business analysis is a complex, inter-disciplinary role that adds value to any ICT initiative, particularly in relation to communication, stakeholder management and requirements management. Careful and deliberate planning is required, using a variety of project management and business analysis tools and techniques, to ensure the successful execution of business analysis activities and maximise stakeholder satisfaction.
Lets take what youve learnt and apply it to a real-world situation.
Activity: Develop
Choose a workplace/industry you already work in or are interested in. Identify a business analysis initiative and answer the following questions:
Plan business analysis approach:
How might you have identified the issue/problem in a real workplace? Explain your answer using a relevant technique to illustrate.
What project management method/technique and associated tools are appropriate?
Formulate at least two objectives of the initiative.
Identify and summarise organisational and legislative requirements applicable to the initiative and business analysis.
Establish applicable business analysis requirements and process needs.
Conduct a stakeholder analysis
Identify all stakeholders related to the business need
classify stakeholders using an appropriate technique
establish how to review and identify new stakeholders
Plan business analysis activities and communication (considering legislation, standards and policies/procedures)
What type of ICT initiative have you selected?
List personnel relevant to the initiative who can contribute to how work will be completed and what work must be completed
Establish the business analysis activities required for the initiative
List the business analysis deliverables
Determine the scope of business analysis activities
Create a project management schedule outline when activities will be performed by the business analyst
Develop estimates for the work required using an appropriate technique
Develop a stakeholder management strategy
Plan stakeholder communication and identify any constraints to the communication
Plan the requirements management process
Establish a requirements repository to store all requirements
List the attributes to be captured
Assess the need for traceability
Determine how to management any changes to requirements
Manage busines analysis performance
List the metrics to measure the work performed by the business analysts
Plan how and when performance will be reported on
Explain:
how to use performance management to determine problems during business analysis activities
potential preventative and corrective action.
RTO No: 91223
-5406891432060
Assessment Task 2
ICTSAD609 Plan and monitor business analysis activities in an ICT environment
Assessment Task 2 Cover Sheet
Student Declaration
To be filled out and submitted with assessment responses I declare that this task is all my own work and I have not cheated or plagiarised the work or colluded with any other student(s).
I understand that if I am found to have plagiarised, cheated or colluded, action will be taken against me according to the process explained to me.
I have correctly referenced all resources and reference texts throughout these assessment tasks.
Student name Student ID number Student signature Date Assessor declaration
I hereby certify that this student has been assessed by me and that the assessment has been carried out according to the required assessment procedures.
Assessor name Assessor signature Date Assessment outcome S NS DNS Resubmission Y N
Feedback
Student result response
My performance in this assessment task has been discussed and explained to me.
I would like to appeal this assessment decision.
Student signature Date A copy of this page must be supplied to the office and kept in the students file with the evidence.
Assessment Task 2: Project PortfolioInformation for students
In this task, you are required to demonstrate your skills and knowledge by working through a number of activities and completing and submitting a project portfolio.
You will need access to:
a suitable place to complete activities that replicates a business environment including a meeting space and computer and internet access
your learning resources and other information for reference
Project Portfolio template
Performance evaluation template.
Ensure that you:
review the advice to students regarding responding to written tasks in the IT Works Student User Guide
comply with the due date for assessment which your assessor will provideadhere with your RTOs submission guidelinesanswer all questions completely and correctly
submit work which is original and, where necessary, properly referenced
submit a completed cover sheet with your workavoid sharing your answers with other students.
ii Assessment information
Information about how you should complete this assessment can be found in Appendix A of the IT Works Student User Guide. Refer to the appendix for information on:
where this task should be completed
how your assessment should be submitted.
Note: You must complete and submit an assessment cover sheet with your work. A template is provided in Appendix B of the Student User Guide. However, if your RTO has provided you with an assessment cover sheet, please ensure that you use that.
Activities
Complete the following activities:
Carefully read the following:
This project requires you to demonstrate your ability to plan and monitor two business analysis activities for business-critical projects in an ICT environment. As part of the assessment you will:
identify and define two business analysis initiatives applicable to business-critical ICT projects
plan an approach to business analysis for each initiative considering requirements laid out in legislation, standards and organisational policies and proceduresconduct a stakeholder analysis to identify and assess stakeholders associated with each initiativeplan business analysis activities including the scope and project management of work to be done and stakeholder communicationplan the requirements management associated with each initiativeestablish and manage business analysis performance.
This project must be based on two separate business analysis initiatives related to an ICT environment with numeric and financial data available to support business analysis planning. You can use the case study business provided to you by your assessor, or you may like to base this on your own business, or a business you are currently working for or are familiar with. It is important that this business has organisational policies and procedures related to your business analysis initiative already developed. Speak to your assessor to get approval if you want to base this on your own business or one you work for.
You will also need to seek input from people who work for, or are involved, in this business analysis initiative several times. Fellow students or your assessor can be involved in these meetings and play the roles of process stakeholders as relevant.
You will be collecting evidence for this unit in a Project Portfolio. The steps you need to take are outlined below.
Project planning
Familiarise yourself with the business youre basing this assessment on and identify two business analysis initiatives applicable to a business-critical ICT project in the business or case study. Make sure your chosen initiatives have numeric and financial data to support business analysis planning.
Complete Page 4 of your Project Portfolio for this unit.
Read through the requirements of Section 1, 2 and 3 of your Project Portfolio as well as the necessary background information, relevant policies and procedures.
Plan business analysis approach
Complete Section 1 of your Project Portfolio.
When you complete Section 1, you need to:
Provide an overview of your chosen business, including:
The name of the business
a description of what the business does
Describe the ICT business analysis initiatives associated with the business, including:
a brief outline of each initiative, illustrated with an appropriate business analysis tool (for example SWAT analysis)
an explanation of how each initiative supports the organisations vision and strategy
two objectives of each initiative.
Establish the legislative and organisational requirements related to each business analysis initiative, including:
a summary of the relevant legislation outlining how it applies to the initiativea summary of applicable standards outlining how it applies to business analysis activitiesa summary of the associated organisational policies and procedures outlining how it applies to business analysis activities.
Identify all stakeholders (using an appropriate technique) for each initiative and:
create a list of key internal and external stakeholders who have authority over business analysis activities
explain how to identify and deal with new stakeholders throughout the duration of each initiative.
Establish applicable organisational process needs, including:
relevant personnel (engagement with staff members on how work should be done)
a description of an appropriate project management method or technique
plan the execution of business analysis activities for each initiative according to organisational requirements.
You are also required to attach certain documents as part of your evidence review the documents you need to attach as outlined in Section 1 of the Project Portfolio and make sure you attach these upon submission.
Make sure you have answered all questions in Section 1. Submit to your assessor for review.
Arrange a meeting with at least one key internal stakeholder and one key external stakeholder. Separate meetings are required for each business analysis initiative. For the purpose of this role-play, your assessor or another student can act as a one or more stakeholders.
Before each meeting, select and familiarise yourself with an applicable business analysis tool (e.g. context diagram) to use as part of the meeting to understand stakeholder requirements.
ii For the purpose of this role-play, your assessor or another student can act as a one or more stakeholders.
Stakeholder meetings
Meet with the key internal and external stakeholders of each initiative. Have separate meetings for each initiative. Take notes so you can complete Section 2 of your Project Portfolio after the meeting. Each meeting should last for approximately 15 mins.
At the meeting:
assess stakeholder attitudes toward the initiative
identify at least two potential risks associated with the stakeholdersdiscuss and establish business analysis deliverables (at least three), including:
descriptions of the deliverables
tasks/activities associated with each deliverableapproval of which activities will be performed and whenstakeholder requirements using the technique selected in step 3.
During the meeting, you will need to demonstrate effective communication skills including:
seeking the views and opinions of others by active listening and questioning
communicating information clearly and concisely
building rapport with stakeholders by positive friendly interaction.
ii This meeting can either be viewed in person by your assessor or you may like to video record the session for your assessor to watch later. Your assessor can provide you with more details at this step. Make sure you follow the instructions above and meet the timeframes allocated.
Plan business analysis activities and communication
Complete Section 2 of your Project Portfolio.
When you complete Section 2, you need to:
Summarise the outcomes of each stakeholder meeting, including:
stakeholder attitudes towards the initiative (including competing demands)
at least two risks associated with the stakeholdersrisk mitigation approach
at a detailed description of at least three business analysis deliverables
stakeholder requirements
Determine business scope for each initiative considering deliverables, associated activities and general stakeholder requirements. Explain how you addressed competing demands.
Develop estimates for business analysis work applicable to each initiative, using numeric and financial information and an appropriate tool/technique for mathematical calculations.
For each stakeholder, plan internal and external stakeholder communication to receive, distribute, access, update and escalate information. Consider at least two communication constraints.
Establish business analysis performance metrics to measure work performed by the business analyst. Identify an appropriate format.
Establish a requirements repository for requirements under development, under review and approved. Include:
a description of the repository
attributes to be capturedidentify key factors outlining the need and process for traceabilitya requirements change process.
You are also required to attach certain documents as part of your evidence review the documents you need to attach as outlined in Section 2 of the Project Portfolio and make sure you attach these upon submission.
ii Assume that a period of time has passed and the business analysis initiative has progressed. A few deliverables have been completed by the business analyst and you are required to assess their performance as part of a continuous improvement effort. Feedback from stakeholders regarding the business analysts deliverable has been positive. The stakeholders have been particularly impressed with the attention to detail in the business analysts work. A number of stakeholders commented on the interpersonal skills of the business analyst, in particular their ability to build rapport and establish a friendly professional relationship with the stakeholders.
Implement your chosen communication system/process or practice (completed earlier in this step) to arrange two separate meetings (for each initiative) with:
at least one stakeholder to discuss progressbusiness analyst to discuss work performance.
Before each stakeholder meeting, update the project schedule to reflect progress to share with stakeholders (you can make assumptions here).
Before each business analyst meeting, assess their performance using the metrics determined earlier in this step (use performance evaluation template if applicable).
Stakeholder update meeting
Meet separately with the relevant stakeholders of each business analysis initiative. Take notes so you can complete Section 3 of your Project Portfolio after the meeting. The meeting should last for approximately 10 minutes.
At the meeting:
share an update on the progress (e.g. via a project schedule)
review and discuss the project progressiondiscuss any changed positions or requirements the stakeholders may haveidentify any new stakeholdersDuring the meeting, you will need to demonstrate effective communication skills including:
seeking the views and opinions of others by active listening and questioning
communicating information clearly and concisely
building rapport with stakeholders by positive friendly interaction.
ii This meeting can either be viewed in person by your assessor or you may like to video record the session for your assessor to watch later. Your assessor can provide you with more details at this step. Make sure you follow the instructions above and meet the timeframes allocated.
Performance management meeting
Meet with the business analyst. Take notes so you can complete Section 3 of your Project Portfolio after the meeting. The meeting should last for approximately 10 minutes.
At the meeting:
discuss the business analysts performance on each business analysis initiative (share the performance evaluation you prepared at the end of step 5 against the metrics established as part of your planning in step 5)
identify where problems may be occurringrecommended corrective actionDuring the meeting, you will need to demonstrate effective communication skills including:
seeking the views and opinions of others by active listening and questioning
communicating information clearly and concisely
building rapport with stakeholders by positive friendly interaction.
ii This meeting can either be viewed in person by your assessor or you may like to video record the session for your assessor to watch later. Your assessor can provide you with more details at this step. Make sure you follow the instructions above and meet the timeframes allocated.
Manage business analysis Complete Sections 3 of your Project Portfolio.
When you complete Section 3 you need to:
Summarise the outcomes of your meeting with the stakeholders for each business analysis meeting, including:
a description of any changed positions or requirements the stakeholder may havea list of any new stakeholders
an explanation of how the changes will be managed.
Summarise the outcomes of your meeting with the business analystConfirm recommendations for corrective action (e.g. via draft email)
Explain how you managed problem solving for business analysis activities drawing on your existing experience.
You are also required to attach certain documents as part of your evidence review the documents you need to attach as outlined in your in Section 3 of the Project Portfolio and make sure you attach these upon submission.
Submit your completed Project Portfolio
Make sure you have completed all sections of your Project Portfolio, answered all questions, provided enough detail as indicated and proofread for spelling and grammar as necessary. Remember to submit all necessary attachments as indicated.
Submit to your assessor for marking.
Assessment Task 2: Checklist
Students name:
Did the student: Completed successfully? Comments
Yes No Plan the business analysis approach, by
Providing an overview of their chosen business, including:
the name of the business
a description of what the business does.
Describe the ICT business analysis initiative associated with the business, including:
a brief outline of two initiatives, illustrated with an appropriate business analysis tool
an explanation of how each initiative supports the organisations vision and strategy
two objectives of each initiative.
Establish the legislative and organisational requirements related to each business analysis initiative, including:
a summary of the relevant legislation outlining how it applies to the initiativea summary of applicable standards outlining how it applies to business analysis activitiesa summary of the associated organisational policies and procedures outlining how it applies to business analysis activities.
Identify all stakeholders (using an appropriate technique) for each initiative and:
create a list of key internal and external stakeholders who have authority over business analysis activities
explain how to identify and deal with new stakeholders throughout the duration of the initiative.
Establish applicable organisational process needs, including:
relevant personnel
engagement with staff members on how work should be donea description of an appropriate project management method or technique.
Plan the execution of business analysis activities according to organisational requirements. Plan business analysis activities and communication for each initiative, by:
Summarising the outcomes of the stakeholder meetings, including:
stakeholder attitudes towards the initiative (including competing demands)
at least two risks associated with the stakeholdersrisk mitigation approach
at a detailed description of at least three business analysis deliverables
stakeholder requirements
Determining business analysis scope for each initiative considering deliverables, associated activities and general stakeholder requirements.
Explaining how they addressed competing demands.
Developing estimates for business analysis work, using numeric and financial information and an appropriate tool/technique for mathematical calculations.
Planning internal and external stakeholder communication to receive, distribute, access, update and escalate information.
Considering at least two communication constraints.
Establishing business analysis performance metrics to measure work performed by the business analyst. Identify an appropriate format.
Establishing a requirements repository for requirements under development, under review and approved, including:
a description of the repository
attributes to be capturedoutline of the need and process for traceabilityrequirements change processPreparing for a stakeholder update meeting for each initiative.
Preparing for performance evaluation meeting. Manage business analysis by:
Summarising the outcomes of their meetings with the stakeholders of each initiative, including:
a description of any changed positions or requirements the stakeholder may havea list of any new stakeholders
an explanation of how the changes will be managed.
Summarising the outcomes of their meeting with the business analyst.
Confirming recommendations for corrective action (e.g. via draft email).
Explaining how they managed problem solving for business analysis activities drawing on their existing experience. Demonstrate effective communication skills including:
seeking the views and opinions of others by active listening and questioning
communicating information clearly and concisely
building rapport with internal and external stakeholders by positive friendly interaction. Task outcome: Satisfactory Not satisfactory
Assessor signature: Assessor name: Date:
Final Results RecordStudent name: Assessor name: Date Final assessment results
Task Type Result
Satisfactory Unsatisfactory Did not submit
Assessment Task 1 Knowledge questions S U DNS
Assessment Task 2 Project Portfolio S U DNS
Overall unit results C NYC Feedback
My performance in this unit has been discussed and explained to me.
I would like to appeal this assessment decision.
Student signature: Date:
I hereby certify that this student has been assessed by me and that the assessment has been carried out according to the required assessment procedures.
Assessor signature: Date:
RTO No: 91223
-5406891432060
Assessment Task 1
ICTSAD609 Plan and monitor business analysis activities in an ICT environment
Assessment Task 1 Cover Sheet
Student Declaration
To be filled out and submitted with assessment responses I declare that this task is all my own work and I have not cheated or plagiarised the work or colluded with any other student(s).
I understand that if I am found to have plagiarised, cheated or colluded, action will be taken against me according to the process explained to me.
I have correctly referenced all resources and reference texts throughout these assessment tasks.
Student name Student ID number Student signature Date Assessor declaration
I hereby certify that this student has been assessed by me and that the assessment has been carried out according to the required assessment procedures.
Assessor name Assessor signature Date Assessment outcome S NS DNS Resubmission Y N
Feedback
Student result response
My performance in this assessment task has been discussed and explained to me.
I would like to appeal this assessment decision.
Student signature Date A copy of this page must be supplied to the office and kept in the students file with the evidence.
Assessment Task 1: Knowledge QuestionsInformation for studentsKnowledge questions are designed to help you demonstrate the knowledge which you have acquired during the learning phase of this unit. Ensure that you:
review the advice to students regarding answering knowledge questions in the IT Works Student User Guide
comply with the due date for assessment which your assessor will provideadhere with your RTOs submission guidelinesanswer all questions completely and correctly
submit work which is original and, where necessary, properly referenced
submit a completed cover sheet with your workavoid sharing your answers with other students.
ii Assessment information
Information about how you should complete this assessment can be found in Appendix A of the IT Works Student User Guide. Refer to the appendix for information on:
where this task should be completed
the maximum time allowed for completing this assessment taskwhether or not this task is open-book.
Note: You must complete and submit an assessment cover sheet with your work. A template is provided in Appendix C of the Student User Guide. However, if your RTO has provided you with an assessment cover sheet, please ensure that you use that.
Questions
Provide answers to all of the questions below:
Describe a general business analysis process. In your answer include:
a definition of business analysis in an ICT environment
steps that outline the business analysis process
examples of business analysis deliverables.
Complete the table outlining legislation, standards and organisational policies and procedures related to business analysis.
Description Example (provide one)
Legislation Standards Policies and procedures List four tools often used in business analysis to identify and understand problems, needs or opportunities in a workplace.
Describe a general project management process. In your answer include:
a definition of project management in an ICT environment
steps that outline the project management process
Summarise two project management techniques that are often associated with an ICT environment. Use the table below for your answer. An example has been provided for you in the first row.
Technique Description
Waterfall This method builds on the classic method and is suitable for more complex projects. It focuses on the sequential performance of tasks. Gantt charts are often used.
Complete the table explaining the types of risk that may be associated with a business analysis initiative and its stakeholders. For each type of risk, you are required to provide an ICT relevant example. The first row has been completed as an example for you to follow.
Type of risk Description Example
Strategic risk These risks can occur at any time and are related to the business or organisations strategy. Initiate process automation throughout the organisation at the expense of personal client relationships and interaction.
Compliance risk Financial risk Operational risk Explain three strategies that may be used to mitigate and manage risks associated with a business analysis initiative. You answer should include:
an explanation of the mitigation strategy
appropriate example to illustrate the strategy.
Complete the table below, outlining a general stakeholder management process.
Step Description of what the step involves Tools/techniques
(provide two per step)
Identify stakeholders Classify stakeholders Develop stakeholder management strategy Plan communication Execute communication
List three communication constraints that may impact stakeholders.
Summarise requirements management as it relates to business analysis. In your answer include:
an explanation of what requirements analysis isoutline of how requirements can be manageda description of four types of requirements
tools or techniques relevant to requirements management.
Define technology solution patterns.
List four metrics that can be used when monitoring business analysis performance.
Assessment Task 1: Checklist
Students name:
Did the student provide a sufficient and clear answer that addresses the suggested answer for the following? Completed successfully? Comments
Yes No Question 1 Question 2 Question 3 Question 4 Question 5 Question 6 Question 7 Question 8 Question 9 Question 10 Question 11 Question 12 Task outcome: Satisfactory Not satisfactory
Assessor signature: Assessor name: Date:
