SIBUSISO DANIEL CHISHALA – BIT22115504
SCHOOL OF SOCIAL SCIENCES, AND TECHNOLOGY
BIT316 – INFORMATION SYSTEMS PROJECT MANAGEMENT
BIT316– ASSIGNMENT
NAME ; SIBUSISO DANIEL CHISHALA
STUDENT NUMBER ; BIT22115504
COURSE CODE; BIT316
EMAIL: Sibuchishla@[Link]
Contacts: 0770710113/0767152745
Lecturer name :
Email @[Link].z
SIBUSISO DANIEL CHISHALA – BIT22115504
### 1. Scrum Roles:
#### **a. Three Core Scrum Roles**
- **Product Owner:**
The Product Owner is responsible for maximizing the value of the product by
managing the Product Backlog. For the JWD Consulting Project Management Intranet
Site project, the Product Owner would prioritize features such as "Ask the Expert"
and "Project management templates" to ensure they deliver the most business value.
They gather requirements from stakeholders and communicate the project vision to
the Development Team.
- **ScrumMaster:**
The ScrumMaster facilitates Scrum processes and removes any obstacles that might
impede the team's progress. For this project, the ScrumMaster would ensure that
Scrum ceremonies like Sprint Planning and Daily Scrums are conducted effectively,
while also addressing challenges such as unclear requirements or team conflicts.
- **Development Team:**
The Development Team is responsible for building and delivering increments of the
product. For the Intranet Site project, this team would consist of developers,
designers, and testers working collaboratively to develop features like templates,
tools, and client-facing articles. They are self-organizing and cross-functional.
#### **b. Interaction Between Roles**
The roles interact continuously to ensure the project’s success:
- **Product Owner & Development Team:** The Product Owner communicates the
requirements to the team and clarifies any questions during the Sprint. For example, if
the team needs more details about the “Ask the Expert” feature, the Product Owner
will provide additional input.
- **ScrumMaster & Development Team:** The ScrumMaster helps the team remain
focused on the Sprint Goal by removing any obstacles, such as technical challenges.
For instance, if there is a delay in integrating a tool, the ScrumMaster coordinates
with other teams or departments to resolve the issue.
SIBUSISO DANIEL CHISHALA – BIT22115504
- **Product Owner & ScrumMaster:** The Product Owner works closely with the
ScrumMaster to ensure that the Product Backlog reflects the most current business
priorities. The ScrumMaster helps the Product Owner understand the team’s velocity
and adjust the backlog accordingly.
### 2. Scrum Artifacts:
#### **a. Purpose and Components**
- **Product Backlog:**
The Product Backlog contains a prioritized list of all the features and requirements
for the project. For the JWD project, this would include items like “Develop project
management templates,” “Create Ask the Expert feature,” and “Integrate third-party
project management tools.”
- **Sprint Backlog:**
The Sprint Backlog is a list of tasks selected from the Product Backlog that the
Development Team commits to completing in a Sprint. For example, if a Sprint is
focused on delivering the “Project management templates,” the Sprint Backlog would
include tasks like “Design template layout” and “Develop template selection
functionality.”
- **Increment:**
The Increment is the sum of all the Product Backlog items completed during the
Sprint, representing a working piece of software. In the JWD project, an Increment
could be a working version of the intranet site with a functional “Ask the Expert”
section and some project management templates.
#### **b. Supporting Project Planning, Tracking, and Delivery**
- **Product Backlog:** Helps in long-term project planning by providing a list of
prioritized tasks. It is updated regularly as new requirements are identified or
priorities shift.
- **Sprint Backlog:** Supports short-term planning and tracking by listing tasks to be
completed in the current Sprint. It is updated daily during the Daily Scrum to reflect
task progress.
SIBUSISO DANIEL CHISHALA – BIT22115504
- **Increment:** Tracks delivery by ensuring that at the end of each Sprint, there is a
potentially shippable product. The Increment is presented during the Sprint Review to
gather feedback from stakeholders.
### 3. Scrum Ceremonies:
#### **a. The Four Main Scrum Ceremonies**
- **Sprint Planning:**
During Sprint Planning, the team decides what can be delivered in the Sprint and
how they will accomplish it. For the JWD project, the team might choose to focus on
building the “Ask the Expert” feature during a Sprint. The Product Owner helps
prioritize tasks, and the Development Team breaks them into manageable chunks.
- **Daily Scrum:**
The Daily Scrum is a 15-minute meeting where team members discuss what they did
the previous day, what they will do today, and any blockers. For the Intranet Site
project, team members might share updates on the design of templates or report any
issues in integrating third-party tools.
- **Sprint Review:**
The Sprint Review occurs at the end of each Sprint, where the team demonstrates the
Increment to stakeholders and gathers feedback. For example, if the "Ask the Expert"
feature is completed, the team would showcase it to JWD Consulting’s management
and adjust the Product Backlog based on their input.
- **Sprint Retrospective:**
The Sprint Retrospective allows the team to reflect on the Sprint and identify
improvements. They discuss what went well, what could be improved, and actionable
steps for the next Sprint. For example, if there was a delay in getting requirements, the
team might decide to involve the Product Owner earlier in the process.
#### **b. Key Activities and Outcomes**
- **Sprint Planning:**
Key activities include defining the Sprint Goal and selecting tasks from the Product
Backlog. The outcome is a clear plan for the Sprint.
SIBUSISO DANIEL CHISHALA – BIT22115504
- **Daily Scrum:**
Activities involve team members providing updates on their progress. The outcome
is a better-aligned team and prompt resolution of issues.
- **Sprint Review:**
The team demonstrates the Increment, and stakeholders provide feedback. The
outcome is an updated Product Backlog reflecting stakeholder priorities.
- **Sprint Retrospective:**
The team identifies improvements and sets action items for the next Sprint. The
outcome is a plan for continuous improvement.
### 4. Unique Scrum Activities by Process Group:
#### **a. Initiation:**
Scrum handles initiation by defining the product vision, creating the initial Product
Backlog, and setting up the Scrum Team. The Product Owner develops a vision,
outlining features like the "Ask the Expert" and templates. The Scrum Team is
formed, with roles assigned based on expertise.
#### **b. Planning:**
Scrum facilitates sprint planning and backlog refinement through regular
collaboration between the Product Owner and the Development Team. Sprint goals
are defined during Sprint Planning, and the Product Backlog is continuously refined
to reflect changes in priorities.
#### **c. Execution:**
Daily Scrums help the team stay aligned and resolve issues quickly. Scrum artifacts
like the Sprint Backlog and Increment are updated to reflect progress. For example, as
the team completes tasks for the "Ask the Expert" feature, the Sprint Backlog is
updated, and the Increment grows.
#### **d. Monitoring and Controlling:**
SIBUSISO DANIEL CHISHALA – BIT22115504
Scrum uses tools like Burndown Charts to track progress, and Sprint Reviews to
monitor whether the project is meeting stakeholder expectations. These tools help
ensure that the project remains on track. If there are any delays, the ScrumMaster
addresses the issue, and adjustments are made to the Sprint Backlog.
#### **e. Closure:**
During project closure, the final Sprint Review and Retrospective are conducted. The
completed project is handed over to stakeholders, and the team reflects on the project,
identifying lessons learned and improvements for future projects.
### 5. Handling Challenges:
#### **a. Potential Challenges and Solutions**
- **Scope Creep:** The Product Owner can address scope creep by maintaining a
well-prioritized Product Backlog and ensuring that only tasks aligned with the
project’s goals are added to the Sprint.
- **Team Conflicts:** The ScrumMaster can facilitate conflict resolution by fostering
open communication and collaboration during Daily Scrums and Retrospectives.
- **Misalignment with Stakeholder Expectations:** Regular Sprint Reviews ensure
continuous feedback, helping to manage and adjust stakeholder expectations
throughout the project.
#### **b. Strategies for Overcoming Obstacles**
- **Scope Creep:** Use a strict definition of done and focus on delivering only
prioritized backlog items.
- **Team Conflicts:** Encourage open communication and address issues early
during Retrospectives.
Misalignment with Stakeholde Regular feedback loops during Sprint Reviews help
ensure that the project stays aligned with stakeholder needs.
This comprehensive approach to applying Scrum methodology ensures successful
management of the JWD Consulting Project Management Intranet Site project.