As aI wantso thatAcceptance criteriaMusic loverA small-sized streaming app with no advertsit doesn’t use up storage space and interrupt my listening experience1. App allows user to stream music without downloading2. App size is 60MB or under3. App offers premium subscription with no adsMusic streaming app userto receive recommendations based upon my current playlistsI can hear new bands that are suited to my taste1. Radio feature created based upon user’s playlists

2. Daily “Have you heard..” notification to be sent to users

Do

Work on high priorities firstBreak down each user story into small and manageable tasks

Don’t

Bite off more than you can chew. Make sure that no one in the team is committing to more than what is feasible to do in the set timeframeTop Tip

Use INVEST to prioritize your user stories. INVEST stands for: I-independent, N-negotiable, V-valuable, E-estimable, S-small, and T-testable

3) The Daily StandupTo make sure that everyone is in sync, the team must meet every day to discuss what they worked on the previous day, what they will work on today and identify any impediments. To make sure that time is used efficiently, the meeting should be timeboxed into a maximum of 15 minutes. The Scrum Master

oversees the meetings and makes sure that the team focuses on the subject at hand.Do

Use burndown charts to track your progress. A burndown chart shows you how much work remains in your sprint and whether you are on scheduleKeep the meeting short and concise. Make sure that everyone is speaking straight to the point

Answer questions like: What have I done since the last Scrum meeting? What do I plan to do before the next meeting? What are the issues I need help with?

Don’t

Bring up topics unrelated to the user stories you’re working on from the backlog

Top Tip

Don’t cancel a Scrum Meeting, even if you are busy or if the attendance is poor. The Daily Scrum meeting is an essential component to a Scrum project. When you cancel one, it becomes easier to cancel others and this disrupts the team’s focus.

Enhance your skills with our expert-led courses

Instructor-ledCertified Scrum Master course £699 +vat See all dates Instructor-ledCertified Scrum Product Owner course £699 +vat

Potential for scope creep

Difficulty in estimating long-term projects.

Kanban

Visualising workflow with Kanban boards
Kanban
uses visual boards to represent work items as they move through different stages of completion.
Principles of Kanban

Key principles include:

Visualise the workflow
Limit Work In Progress (WIP)
Manage flow
Make process policies explicit

Implement feedback loops.

Industries benefiting from Kanban

Kanban is versatile and can be applied in various sectors, including software development, marketing and design, human resources, and manufacturing.

Extreme Programming (XP)

Key practices and values

emphasises technical excellence and customer satisfaction. Core practices include pair programming, test-driven development, continuous integration, and small, frequent releases.

Best scenarios for XP implementation

XP is particularly effective for projects with changing requirements, small to medium-sized development teams, and environments that value close collaboration with customers.

Crystal

Crystal Red.

Each variant is designed for different team sizes and project criticality.

A tight deadline may lead to a rushed project, resulting in lower quality outputs.

Identify and include all relevant costs and benefits, both tangible and intangibleA limited budget may result in a project being understaffed or under-resourced, which may also affect quality.Use realistic and consistent assumptions and data sourcesA project with an overambitious scope can strain resources and time, leading to poor results.

Involve subject matter experts in the analysis processSuccessful project management involves finding the right balance and making trade-offs between the three constraints while maintaining the desired level of quality. By understanding the impact of these constraints on each other, project managers can make informed decisions to lead the Review and update the CBA regularly to reflect changes in the project or environment.project

Common pitfalls to a successful outcome.Overlooking or underestimating hidden or long-term costs or benefitsBenefits of using the project management triangle

Overestimating the benefits or underestimating the costsUtilising the project management triangle provides some distinct benefits to the project team and stakeholders. These are as follows.Not considering alternative options or the status quoEasier change management

Not accounting for risks and uncertainties.The triangle model helps to Resource levellingmake changes easier

Resource levelling is a technique for managing project resources to achieve optimal resource utilisation. It involves adjusting the allocation of resources to tasks so that resource demand does not exceed the available supply. By smoothing out the use of resources, resource levelling can reduce overallocation and idle time.Course manual where applicable.. This is because if a change arises, the project managers can easily evaluate how this change will affect the scope, time and cost, decide, as such it helps to quickly evaluate a change request, understand the ripple effects, and make an informed decision on change.Priority clarification

Visualising the three constraints helps to

clarify priorities

. This will make it possible for the team to quickly identify important elements in the project, direct resources to important tasks and make trade-offs as required based on the project goals.

Improved client communication

The triangle is a helpful

communication tool

to both communicate with and educate clients. The project managers can use the triangle to show the project’s constraints to the clients, visualise how changes would affect them, and set realistic expectations regarding project deliverables.

Risk reduction

Utilising the triangle will help in

ITIL Foundation training courses - learning outcomes