Agile project- part(1) Agile proposal
Group (8) Names:
Mohammad Alqawasmeh (301334309)
Obieda bani Ismail (301334308)
Hatem Rahmeh (301272645)
Husam Al-Shraydeh (301213010)
Note: the other two students did not respond to participate in the assignment
Centennial College
Agile Project Management And Requirements Management (Sec.005)
Professor Hector Garza
Assignment Due Date: 27, 2023 11:59 PM
Stakeholder Register
Area/Team/Group
Influence
Interest
Concerns
High/Med/Low
High/Med/Low
Sales team
High
High
Difficulty using the current POS system, which leads to
human errors and delays in sales
Supply team
High
High
Inaccuracy of inventory data from the current POS-ERP
integration, leading to over/under stocking of product
Finance and
Accounting team
High
High
Inaccurate sales and waste data from existing POS-ERP
integration, resulting in inaccurate reporting
Pricing team
Med
High
Lack of centralization in pricing updates across all sites
Management
High
High
Lack of reliable data from the current POS system, which
hinders decision making
Replenishment
team
Med
High
Lack of real-time inventory data from the existing POS
system, which leads to delays in restocking
Sponsors
High
Low
not available to hear team members’ concerns at any time
Owners
Low
High
Lack of information and analysis before planning
Customers
High
Low
don't know about the organizational changes taking place
Governments
High
Low
Project members
Med
Med
Lack of data and taxation information
Poor communication and collaboration,
Lack of training and education
Assumption:
1- Assumption: All necessary resources will be provided:
Description: This assumption is that the necessary resources, such as funding, personnel, and
equipment, will be provided in order to complete the project as planned.
Relevance: Without these resources, the project may not be able to be completed on time or within
budget.
Impact if true: The project will have a higher chance of success.
Impact if false: The project may face delays or budget overruns.
2- Assumption: The sales team will be able to provide adequate feedback on the POS system
Description: This assumption is that the sales team will be able to provide feedback on the POS
.system that will help to improve its usability
Relevance: Feedback from the sales team is crucial to making the POS more user-friendly for
them.
Impact if true: The POS will be more user-friendly for the sales team.
Impact if false: The POS may not be as user-friendly as intended.
3 - Assumption: The ERP system will be able to handle the increased data flow
Description: This assumption is that the ERP system will be able to handle the increased data
flow that will come with the improved integration with the POS system.
Relevance: If the ERP system is not able to handle the increased data flow, it may lead to errors
or delays in the system.
Impact if true: The integration with the ERP system will be improved.
Impact if false: The integration with the ERP system may not be as effective as intended.
4 - Assumption: The replenishment system will be able to integrate with the POS system
Description: This assumption is that the replenishment system will be able to integrate with the
POS system in a way that will trigger deliveries according to inventory levels.
Relevance: This integration is crucial to the project, as it will help to ensure that inventory levels
are maintained at each site.
Impact if true: The replenishment system will be able to trigger deliveries according to inventory
levels.
Impact if false: The replenishment system may not be able to integrate with the POS system,
leading to issues with inventory levels.
5 -Assumption: The pricing system will be able to integrate with the POS system
Description: This assumption is that the pricing system will be able to integrate with the POS
system in a way that will allow for centralized price updates for all sites.
Relevance: This integration will help to ensure that all sites have the most up-to-date pricing
information.
Impact if true: The pricing system will be able to integrate with the POS system, allowing for
centralized price updates.
Impact if false: The pricing system may not be able to integrate with the POS system, leading to
issues with pricing at the different sites.
6 - Assumption: All existing POS systems will be compatible with the new POS system
Description: This assumption is that all existing POS systems will be compatible with the new
POS system in order for it to be expanded to 700 sites.
Relevance: Without compatibility with existing systems, the new POS system may not be able to
be expanded to all sites.
Impact if true: The new POS system will be able to be expanded to all 700 sites.
Impact if false: The new POS system may not be able to be expanded to all sites, leading to
issues with consistency across the company.
SWOT Analysis of using Agile in this project
Strengths:
Agile approach allows for flexibility and adaptability to changes, which is important in a project
with multiple stakeholders and a complex system.
Agile approach allows for faster delivery of working software, which can help to alleviate some
of the pain points currently experienced by the Sales team.
Agile approach allows for a more collaborative and transparent working process, which can help
to build trust and alignment between the IT, Sales, Supply, Finance, and Accounting teams.
Weaknesses:
Agile approach may be new and unfamiliar to some team members, which can lead to a learning
curve and initial resistance.
Agile approach requires a high degree of discipline and commitment from all team members in
order to be successful.
Agile approach may be more difficult to manage and control compared to traditional Waterfall
approach.
Opportunities:
Agile approach can provide a platform for innovation and experimentation, which can lead to new
ideas and solutions for the project goals.
Agile approach can help to build a more engaged and motivated team, which can improve
productivity and quality of work.
Threats:
Agile approach can lead to scope creep and a lack of clear deliverables, which can increase costs
and delay the project.
Agile approach can lead to a lack of visibility and control for stakeholders, which can create
resistance and mistrust.
Risk register
Risk
Impact
Probability
Owner
Mitigation Plan
Lack of adequate resources for the
project
Delays or
budget
overruns
High
Project
Manager
Regularly monitor resource allocation
and budget, and request additional
resources as needed
Sales team not providing adequate
feedback on the POS system
POS system
may not be
as userfriendly as
intended
Medium
Project
Manager
Regularly gather feedback from the
sales team, and involve them in the
design and testing process
ERP system not able to handle the
increased data flow
Errors or
delays in the
system
High
IT team
Test the integration between the POS
and ERP systems before deployment
and regularly monitor the system
performance during the
implementation phase
Replenishment system not being able
to integrate with the POS system
Difficulty in
triggering
deliveries
according to
inventory
levels
High
IT team
Test the integration between the POS
and replenishment systems before
deployment and involve the
replenishment team in the design and
testing process
Remaining 350 sites not willing to
adopt the POS system
Difficulty in
expanding
the system to
all 700 sites
as planned
Medium
Project
Manager
Mitigation Plan: Regularly
communicate the benefits of the POS
system to the remaining sites and
involve representatives from those
sites in the design and testing process
Essay:
In this part, we will talk about agile ideology in general and why it is the best choice for this
project. Agile is the best approach to deliver this project for several reasons:
Firstly, Agile values customer collaboration and working software over comprehensive
documentation, which aligns well with the needs of the Sales team who are the primary users of
the POS system. The Sales team has expressed dissatisfaction with the current system, stating
that it is too complicated and results in human errors. Agile approaches such as Scrum, which
emphasizes frequent inspection and adaptation, will allow the team to work closely with the
Sales team to understand their needs and continuously improve the user experience of the POS
system. Agile project management states the breakdown of the project into small tasks and stages
and sprints. Each stage of these sprints consists of loops, which are planning, designing, testing,
releasing or planning again. From these steps our product will have fewer errors so the
integration between the different sections in the company will be achieved, and also the
efficiency of the company work will be increased as well, in addition, that we will have the
satisfaction of the customers as much as we can. Scrum and kanban are methodologies of agile
ideology. They will be mentioned in this paper in addition to the strong relationship between the
product and customer reviews, in which we can use continuous feedback to make our product
more effective. Agile is a project management methodology that emphasizes flexibility,
collaboration, and continuous improvement. It is an approach that is well-suited to deliver
projects in a fast-paced, rapidly-changing environment, such as the one we find ourselves in
today. In this essay, I will explain why Agile is the best approach to delivering our project, and
how it can help us to achieve our goals and objectives. One of the key reasons why Agile is the
best approach to deliver our project is its flexibility. Agile is a methodology that is designed to
adapt to changing circumstances and requirements. This means that we can respond quickly to
changes in the project environment, such as changes in customer needs or market conditions. For
example, if we find that our customers are requesting new features that we did not anticipate, we
can easily incorporate these changes into the project without disrupting the overall schedule or
budget. This flexibility is crucial in today's fast-paced business environment, where change is the
norm, and organizations need to be able to adapt quickly in order to stay competitive. Another
key advantage of Agile is its collaborative approach. Agile is based on the principle of "working
software over comprehensive documentation." This means that the focus is on delivering
working software that meets customer needs, rather than on extensive documentation and
planning.
Secondly, Agile approaches prioritize flexibility and adaptability, which is crucial for the
success of this project. The current integration between the POS and ERP systems is not reliable,
and the teams responsible for replenishment and pricing have specific requirements for
integration with their own systems. Agile methodologies such as Kanban, which focuses on
visualizing and managing workflow, will allow the team to easily adapt to changing
requirements and integrate with multiple systems. Another important aspect of Agile is its focus
on customer involvement. Agile encourages active participation from customers throughout the
project, which helps to ensure that we deliver a product that meets their needs. This customer
involvement can take many forms, such as user stories, acceptance criteria, and customer
feedback. By involving customers in the project, we can ensure that we are creating a product
that meets their needs and that they will be happy with. Agility is key to achieving this. If you
are working on a website that relies on user input, then Agility is essential. By making requests
quickly and showing an accurate response time, your users will be likelier to stick around and
leave a positive review. Agile software development eXtreme Programming and Scrum.
Addison-Wesley Professional. The Sales team has expressed dissatisfaction with the current
system, stating that it is too complicated and results in human errors. Agile approaches such as
Scrum, which emphasizes frequent inspection and adaptation, will allow the team to work
closely with the Sales team to understand their needs and continuously improve the user
experience of the POS system, in addition to the strong relationship between the product and
customer reviews, in which we can use the continuous feedback to make our product more
effective. Agile project management state the breakdown of the project into small tasks and
stages and sprint; each stage of these sprints consist of loops, these loops are planning, designing,
testing, releasing or planning again; from these steps, our product will have fewer errors so the
integration between the different sections in the company will be achieved, and also the
efficiency of the company work will be increased as well, in addition, that we will have the
satisfaction of the customers as much as we can. Scrum and kanban are a methodology of agile
ideology, and they will be mentioned in this paper. Another key advantage of Agile is its
collaborative approach. Agile is based on the principle of "working software over comprehensive
documentation." This means that the focus is on delivering working software that meets
customer needs, rather than on extensive documentation and planning. This collaborative
approach encourages team members to work together closely and to share ideas and feedback
throughout the project. This helps to ensure that everyone is working towards the same goal and
that any problems or issues that arise are quickly identified and addressed. Agile also promotes
continuous improvement. This means that we can learn from our mistakes and continuously
improve our processes and practices. For example, if we find that a particular feature is causing
problems, we can quickly address the issue and make changes to improve the overall quality of
the software.
Finally, Agile approaches are well-suited for projects with a high degree of uncertainty
and complexity, such as expanding the POS system to 700 sites. As stated by Scrum co-creator
Jeff Sutherland, "Scrum is a framework that helps teams work together to accomplish a goal...
It's light, simple, and easy to understand. And it works" (Sutherland, 2014). The Agile approach
will allow the team to break down the project into manageable chunks, prioritize the most
important tasks, and continuously improve the system as it is implemented in each site. Another
key advantage of Agile is its collaborative approach. Agile is based on the principle of "working
software over comprehensive documentation." This means that the focus is on delivering
working software that meets customer needs, rather than on extensive documentation and
planning. This collaborative approach encourages team members to work together closely and to
share ideas and feedback throughout the project. This helps to ensure that everyone is working
towards the same goal and that any problems or issues that arise are quickly identified and
addressed. Agile also promotes continuous improvement. This means that we can learn from our
mistakes and continuously improve our processes and practices. For example, if we find that a
particular feature is causing problems, we can quickly address the issue and make changes to
improve the overall quality of the software. This continuous improvement approach helps to
ensure that the final product is of the highest quality and that it meets the needs of our customers.
One of the key ways that Agile helps to deliver projects is through its use of iterative and
incremental development. This means that we divide the project into smaller, manageable
chunks, and deliver working software at the end of each iteration. This approach helps to ensure
that we are making progress and that we are delivering value to our customers. It also allows us
to get feedback from our customers early on, which helps to ensure that we are meeting their
needs.
Another important aspect of Agile is its focus on customer involvement. Agile encourages active
participation from customers throughout the project, which helps to ensure that we deliver a
product that meets their needs. This customer involvement can take many forms, such as user
stories, acceptance criteria, and customer feedback. By involving customers in the project, we
can ensure that we are creating a product that meets their needs and that they will be happy with.
In conclusion, Agile approaches such as Scrum and Kanban align well with the goals and
challenges of this project and provide a flexible and adaptable framework for delivering a
successful POS expansion. In addition, it is the best ideology to make control projects variables
and make it related to the owner, sponsor and customer satisfaction because in every result we
need to show up this product and make a review about our product. These reviews will be used
to update our product design continuously until we meet the needed requirements.
References
Sutherland, J., & Sutherland, J. J. (2014). Scrum: the art of doing twice the work in half the time.
Currency. Development. Retrieved from
https://books.google.ca/books?hl=en&lr=&id=RoPZCwAAQBAJ&oi=fnd&pg=PR7&dq=Suther
land,+J.+(2014,+February+26).+Scrum&ots=baa3Mgvg0O&sig=wihYcdRhMFRfAEh7uXM9rF
N-hZc#v=onepage&q&f=false
Rodríguez-Sedano, F. J., Conde, M. Á., & Fernández-Llamas, C. (2018, July). Measuring
teamwork competence development in a multidisciplinary project based learning environment.
In International Conference on Learning and Collaboration Technologies (pp. 466-479).
Springer, Cham.
https://link.springer.com/chapter/10.1007/978-3-319-91743-6_34
Beck, K., & Fowler, M. (2001). Planning extreme programming. Addison-Wesley Professional.
https://books.google.ca/books?hl=en&lr=&id=u13hVoYVZa8C&oi=fnd&pg=PR11&dq=Beck,+
K.+(2001).+Extreme+programming+&ots=GN380VcSgh&sig=HJPDKL7HsXGAnjqCpgpVgV
p_mMk#v=onepage&q&f=false
Highsmith, J. A., & Highsmith, J. (2002). Agile software development ecosystems. AddisonWesley Professional.
https://books.google.ca/books?hl=en&lr=&id=uE4FGFOHs2EC&oi=fnd&pg=PR15&dq=Highs
mith,+J.+A.+(2002).+Agile+software&ots=OO_KuE2v1p&sig=liLvhkksCHjo1_zZTo7wcZsX6k#v=onepage&q&f=false