Unit 9: IT Project Management
Assignment 2: Project Management in Action
Alisha Nasir
20233767
1
,Table of Contents
Project outline:......................................................................................................................................3
Client requirements:..............................................................................................................................3
Scope of the project:.............................................................................................................................3
Methodology for the project:................................................................................................................4
Methodology 1 (Waterfall):...............................................................................................................4
Methodology 2 (Agile):......................................................................................................................4
Chosen methodology justification:....................................................................................................5
Researching possible solutions:.............................................................................................................6
Solution 1:..........................................................................................................................................6
Risks and limitations of solution 1:....................................................................................................6
Solution 2:..........................................................................................................................................6
Risks and limitations of solution 2:....................................................................................................6
Justification of final solution:.............................................................................................................7
Feasibility study:....................................................................................................................................8
Technical assessment:.......................................................................................................................8
Economic:..........................................................................................................................................8
Legal:.................................................................................................................................................8
Operational:.......................................................................................................................................8
Scheduling:........................................................................................................................................8
Functional Requirements:..................................................................................................................8
Non-functional Requirement:............................................................................................................9
Project plan:..........................................................................................................................................9
Gantt chart:........................................................................................................................................9
Storyboard:......................................................................................................................................10
Flow chart:.......................................................................................................................................13
Assets table:.....................................................................................................................................14
Test plan (Initial):.............................................................................................................................17
Final product:.......................................................................................................................................18
Work log:.............................................................................................................................................19
Revised Gantt chart:............................................................................................................................20
Justification:.....................................................................................................................................20
Test plan(final):....................................................................................................................................21
Feedback questionnaires:....................................................................................................................27
Improvements based off feedback:.....................................................................................................28
2
, Feedback improvement #1:.............................................................................................................28
Feedback improvement #2:.............................................................................................................29
Feedback improvement #3:.............................................................................................................30
References:..........................................................................................................................................31
Project outline:
My goal for this task is to create a fully functioning website for the company A&S Cakes. A&S Cakes is
a small cake decorating business who would like to expand their company therefore have asked for a
website alongside with requirements. I will be deciding on the methodology that I will use for this
project and discuss the risks and constraints of each methodology; documenting my progress as I go
along.
Client requirements:
Include pictures of products
Social media links
5 Pages
Easy navigation
Use of company logo
Cake purchase form
Contact page for queries
Scope of the project:
The scope of this project involves creating a visually appealing and user friendly website with five
pages: Home, About, Gallery, Bookings, and Contact. The website will feature images to showcase
the company's products, cakes, helping customers visualise possible purchases. It will also include
social media links, specifically on the home page, to allow customers to engage with the company on
various platforms and share its content. Easy navigation is critical, ensuring users can smoothly
browse through the pages.
Additionally, the website will display the company’s logo to reinforce brand identity. The site will
also include a cake purchase form on the Bookings page, allowing customers to easily place orders
by discussing cake preferences, sizes, and other details. Finally, a Contact page for queries will
provide a form for customer enquiries, ensuring direct communication for any questions or
feedback, alongside relevant contact information such as phone numbers and email addresses so
that the company can contact the users.
3
,Methodology for the project:
Methodology 1 (Waterfall):
The Waterfall methodology can be effective for smaller projects in web development where
requirements are clear and often have been set at the start of the project. The linear structure
means that phases such as requirements gathering, design, implementation, testing, and
maintenance happen in a sequence. This approach can be beneficial when working with clients and
stakeholders who would like regular updates on the websites created. Since each phase must be
completed before moving on, it’s easier to track progress and ensure that everyone is achieving their
goals. However, the inflexibility of the Waterfall model can create problems for projects that might
need adjustments. If user feedback needs changes during development, it can be difficult to
accommodate these without going back to earlier phases.
An example of using the Waterfall methodology in web development is the creation of an e-
commerce website for a small business. The project begins with requirements gathering, where the
client specifies their needs, such as a homepage, product pages, contact page, and payment
integration. Next, in the design phase, the team produces design plans, which the
clients/stakeholder’s reviews and approves. Following that, the implementation phase involves
developers building the site sequentially, starting with the homepage and moving through the
product pages to the checkout process. Once development is complete, the testing phase ensures all
intended functions work. After successful testing, the website is deployed to a live server, making it
accessible to users to test and address bugs. Finally, during the maintenance phase, any bugs or
minor updates are addressed.
Methodology 2 (Agile):
Agile is a flexible project management methodology particularly suited for web development
projects that need adaptations often and quick responses to change. In Agile, projects are divided
into small, manageable units called sprints, usually lasting two to four weeks. During each sprint,
development teams focus on delivering specific features or components of the website, such as a
new feature or interface component. Regular feedback from stakeholders is crucial in this process,
allowing teams to adjust based on user input and constant changing requirements. Agile emphasises
continuous improvement, with teams reflecting on their performance at the end of each sprint to
identify areas for improvement. This approach allows for better collaboration among team
members, and improves the project's responsiveness to changing needs, ultimately making it very
flexible. Due to its quick nature to change, it is also the more cost-effective approach.
An example of using the Agile methodology in web development is the creation of a restaurant
website. The project starts with a meeting to gather initial requirements, after which the team
breaks the work into two-week sprints. In the first sprint, they might focus on developing the
homepage and basic navigation. During the sprint, they hold daily meetings to discuss progress and
address any problems. At the end of the sprint, they present the completed homepage to
stakeholders for feedback, allowing the team to adjust based on user input, such as adding a
reservation button. In following sprints, the team addresses features like the menu page, an online
ordering system, and a contact form, continuously refining the site based on ongoing feedback.
4
, Chosen methodology justification:
The Waterfall methodology suits the project to create a fully functioning website for A&S Cakes, as
there are a few key factors in this methodology that fit well according to the needs and scope of this
project. The clearly defined requirements of the project include: specific pages—Home, About,
Gallery, Bookings, Contact; product images; social media links; and a cake-purchasing form. The
waterfall method can be effective where requirements are stable and known upfront, hence
allowing an organised approach for development. Due to its linear structure, each phase can be
gone through step by step. This ensures that the given phase is thoroughly completed before
proceeding to the next, a feature which is beneficial for this website since it is a small project.
Further, the use of Waterfall allows for easy tracking of progress; hence, project managers are able
to be in control of timelines and budgets involved in the process while ensuring that A&S Cakes gets
predictable outcomes as teams work on launching the website. Moreover, detailed documentation
throughout the project life cycle ensures that changes or updates in the design and development
process are easily executed in the future. Moreover, even though Waterfall is more rigid, it still
allows for customer involvement at some critical stages so A&S Cakes can review and approve the
design and functionality of the website before moving forward.
Agile may not be the best fit for creating a fully functioning website for A&S Cakes, for several
reasons. First, Agile thrives in environments where requirements are likely to change often and
where continuous feedback is vital. In contrast, this project has clearly defined requirements, such as
specific pages and features, which do not appear likely to change significantly during development.
This stability makes it more suitable for a linear approach like Waterfall, as it allows the team to
focus on completing each phase thoroughly before moving on.
Moreover, the iterative nature that characterises Agile will also introduce problems that are not
needed in such a small project. The need for frequent stakeholder feedback and continuous
adjustments might make timelines and budgets more complicated, where Waterfall provides more
predictability. The clear emphasis on documentation in Waterfall also more readily supports future
updating and changes, where one traceably pursues the process by having a clear record. Finally,
while Agile allows for collaboration and flexibility, Waterfall's structured approach will allow the
client to be involved at key milestones—meaning A&S Cakes will be confident in the designs and
functionalities they approve before finalising the site. In all, the organised and predictable nature of
Waterfall does match more with the given needs and scope of the A&S Cakes website project.
5
Assignment 2: Project Management in Action
Alisha Nasir
20233767
1
,Table of Contents
Project outline:......................................................................................................................................3
Client requirements:..............................................................................................................................3
Scope of the project:.............................................................................................................................3
Methodology for the project:................................................................................................................4
Methodology 1 (Waterfall):...............................................................................................................4
Methodology 2 (Agile):......................................................................................................................4
Chosen methodology justification:....................................................................................................5
Researching possible solutions:.............................................................................................................6
Solution 1:..........................................................................................................................................6
Risks and limitations of solution 1:....................................................................................................6
Solution 2:..........................................................................................................................................6
Risks and limitations of solution 2:....................................................................................................6
Justification of final solution:.............................................................................................................7
Feasibility study:....................................................................................................................................8
Technical assessment:.......................................................................................................................8
Economic:..........................................................................................................................................8
Legal:.................................................................................................................................................8
Operational:.......................................................................................................................................8
Scheduling:........................................................................................................................................8
Functional Requirements:..................................................................................................................8
Non-functional Requirement:............................................................................................................9
Project plan:..........................................................................................................................................9
Gantt chart:........................................................................................................................................9
Storyboard:......................................................................................................................................10
Flow chart:.......................................................................................................................................13
Assets table:.....................................................................................................................................14
Test plan (Initial):.............................................................................................................................17
Final product:.......................................................................................................................................18
Work log:.............................................................................................................................................19
Revised Gantt chart:............................................................................................................................20
Justification:.....................................................................................................................................20
Test plan(final):....................................................................................................................................21
Feedback questionnaires:....................................................................................................................27
Improvements based off feedback:.....................................................................................................28
2
, Feedback improvement #1:.............................................................................................................28
Feedback improvement #2:.............................................................................................................29
Feedback improvement #3:.............................................................................................................30
References:..........................................................................................................................................31
Project outline:
My goal for this task is to create a fully functioning website for the company A&S Cakes. A&S Cakes is
a small cake decorating business who would like to expand their company therefore have asked for a
website alongside with requirements. I will be deciding on the methodology that I will use for this
project and discuss the risks and constraints of each methodology; documenting my progress as I go
along.
Client requirements:
Include pictures of products
Social media links
5 Pages
Easy navigation
Use of company logo
Cake purchase form
Contact page for queries
Scope of the project:
The scope of this project involves creating a visually appealing and user friendly website with five
pages: Home, About, Gallery, Bookings, and Contact. The website will feature images to showcase
the company's products, cakes, helping customers visualise possible purchases. It will also include
social media links, specifically on the home page, to allow customers to engage with the company on
various platforms and share its content. Easy navigation is critical, ensuring users can smoothly
browse through the pages.
Additionally, the website will display the company’s logo to reinforce brand identity. The site will
also include a cake purchase form on the Bookings page, allowing customers to easily place orders
by discussing cake preferences, sizes, and other details. Finally, a Contact page for queries will
provide a form for customer enquiries, ensuring direct communication for any questions or
feedback, alongside relevant contact information such as phone numbers and email addresses so
that the company can contact the users.
3
,Methodology for the project:
Methodology 1 (Waterfall):
The Waterfall methodology can be effective for smaller projects in web development where
requirements are clear and often have been set at the start of the project. The linear structure
means that phases such as requirements gathering, design, implementation, testing, and
maintenance happen in a sequence. This approach can be beneficial when working with clients and
stakeholders who would like regular updates on the websites created. Since each phase must be
completed before moving on, it’s easier to track progress and ensure that everyone is achieving their
goals. However, the inflexibility of the Waterfall model can create problems for projects that might
need adjustments. If user feedback needs changes during development, it can be difficult to
accommodate these without going back to earlier phases.
An example of using the Waterfall methodology in web development is the creation of an e-
commerce website for a small business. The project begins with requirements gathering, where the
client specifies their needs, such as a homepage, product pages, contact page, and payment
integration. Next, in the design phase, the team produces design plans, which the
clients/stakeholder’s reviews and approves. Following that, the implementation phase involves
developers building the site sequentially, starting with the homepage and moving through the
product pages to the checkout process. Once development is complete, the testing phase ensures all
intended functions work. After successful testing, the website is deployed to a live server, making it
accessible to users to test and address bugs. Finally, during the maintenance phase, any bugs or
minor updates are addressed.
Methodology 2 (Agile):
Agile is a flexible project management methodology particularly suited for web development
projects that need adaptations often and quick responses to change. In Agile, projects are divided
into small, manageable units called sprints, usually lasting two to four weeks. During each sprint,
development teams focus on delivering specific features or components of the website, such as a
new feature or interface component. Regular feedback from stakeholders is crucial in this process,
allowing teams to adjust based on user input and constant changing requirements. Agile emphasises
continuous improvement, with teams reflecting on their performance at the end of each sprint to
identify areas for improvement. This approach allows for better collaboration among team
members, and improves the project's responsiveness to changing needs, ultimately making it very
flexible. Due to its quick nature to change, it is also the more cost-effective approach.
An example of using the Agile methodology in web development is the creation of a restaurant
website. The project starts with a meeting to gather initial requirements, after which the team
breaks the work into two-week sprints. In the first sprint, they might focus on developing the
homepage and basic navigation. During the sprint, they hold daily meetings to discuss progress and
address any problems. At the end of the sprint, they present the completed homepage to
stakeholders for feedback, allowing the team to adjust based on user input, such as adding a
reservation button. In following sprints, the team addresses features like the menu page, an online
ordering system, and a contact form, continuously refining the site based on ongoing feedback.
4
, Chosen methodology justification:
The Waterfall methodology suits the project to create a fully functioning website for A&S Cakes, as
there are a few key factors in this methodology that fit well according to the needs and scope of this
project. The clearly defined requirements of the project include: specific pages—Home, About,
Gallery, Bookings, Contact; product images; social media links; and a cake-purchasing form. The
waterfall method can be effective where requirements are stable and known upfront, hence
allowing an organised approach for development. Due to its linear structure, each phase can be
gone through step by step. This ensures that the given phase is thoroughly completed before
proceeding to the next, a feature which is beneficial for this website since it is a small project.
Further, the use of Waterfall allows for easy tracking of progress; hence, project managers are able
to be in control of timelines and budgets involved in the process while ensuring that A&S Cakes gets
predictable outcomes as teams work on launching the website. Moreover, detailed documentation
throughout the project life cycle ensures that changes or updates in the design and development
process are easily executed in the future. Moreover, even though Waterfall is more rigid, it still
allows for customer involvement at some critical stages so A&S Cakes can review and approve the
design and functionality of the website before moving forward.
Agile may not be the best fit for creating a fully functioning website for A&S Cakes, for several
reasons. First, Agile thrives in environments where requirements are likely to change often and
where continuous feedback is vital. In contrast, this project has clearly defined requirements, such as
specific pages and features, which do not appear likely to change significantly during development.
This stability makes it more suitable for a linear approach like Waterfall, as it allows the team to
focus on completing each phase thoroughly before moving on.
Moreover, the iterative nature that characterises Agile will also introduce problems that are not
needed in such a small project. The need for frequent stakeholder feedback and continuous
adjustments might make timelines and budgets more complicated, where Waterfall provides more
predictability. The clear emphasis on documentation in Waterfall also more readily supports future
updating and changes, where one traceably pursues the process by having a clear record. Finally,
while Agile allows for collaboration and flexibility, Waterfall's structured approach will allow the
client to be involved at key milestones—meaning A&S Cakes will be confident in the designs and
functionalities they approve before finalising the site. In all, the organised and predictable nature of
Waterfall does match more with the given needs and scope of the A&S Cakes website project.
5
