Agile Business Analysis - Requirements and Management Folio of Work
VerifiedAdded on  2023/01/16
|13
|3076
|73
AI Summary
This document is an analysis of the Sam Bot project, an online chat system for students. It includes information on the project's background, business goals, stakeholders, product vision, and requirements. The document also covers the agile approach used in the project and stakeholder communication.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Agile Business Analysis
Requirements and Management Folio of
Work
Project: Name of project
Name of Client
Author: Name
S Number: Number
Workshop: Day, Time, Instructor
Requirements and Management Folio of
Work
Project: Name of project
Name of Client
Author: Name
S Number: Number
Workshop: Day, Time, Instructor
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Table of Contents
1 Introduction...............................................................................1
1.1 Purpose of this Document.......................................................................1
1.2 Scope of this document..........................................................................1
1.3 Background...........................................................................................1
2 Business Goals............................................................................1
2.1 Agile Approach.....................................................................................2
3 Stakeholders...............................................................................2
3.1 Stakeholder Definition...........................................................................2
3.2 Stakeholder Communication...................................................................4
4 Product Vision............................................................................4
4.1 Vision Statement...................................................................................4
4.2 Product Road Map.................................................................................5
5 Requirements.............................................................................6
5.1 Story Mapping.......................................................................................6
5.2 Story Decomposition..............................................................................6
6 Delivery and Review...................................................................9
7 Project Management...................................................................9
7.1 APM Framework...................................................................................9
8 References.............................................................................10
1 Introduction...............................................................................1
1.1 Purpose of this Document.......................................................................1
1.2 Scope of this document..........................................................................1
1.3 Background...........................................................................................1
2 Business Goals............................................................................1
2.1 Agile Approach.....................................................................................2
3 Stakeholders...............................................................................2
3.1 Stakeholder Definition...........................................................................2
3.2 Stakeholder Communication...................................................................4
4 Product Vision............................................................................4
4.1 Vision Statement...................................................................................4
4.2 Product Road Map.................................................................................5
5 Requirements.............................................................................6
5.1 Story Mapping.......................................................................................6
5.2 Story Decomposition..............................................................................6
6 Delivery and Review...................................................................9
7 Project Management...................................................................9
7.1 APM Framework...................................................................................9
8 References.............................................................................10
1 Introduction
1.1 Purpose of this Document
The document is an analysis document for the Sam Bot project. Sam Bot is an online
chat system for students and the document includes the background details of the
project along with the information on the business goals, vision, stakeholders,
requirements, and delivery.
1.2 Scope of this document
The scope of the document is to cover the analysis details of the project to present the
information on the project background and goals along with the high-level details of
the project requirements, approach, stakeholders, and delivery.
The document will include the approach that will be used in the project followed by
the details of the primary stakeholders involved. The stakeholder definition and
communication will be included. The report will also cover the product vision in
terms of the vision statement and product road map. The requirements, project
delivery & review, and project management details will be covered as well.
1.3 Background
The project is Sam Bot which is an online-chat system being developed for the
students. The system will allow the students to place their queries and these will be
resolved by the administrator on a real-time basis. It is a chat bot that will be
developed and implemented to make sure that the overall turnaround time for query
resolution is reduced and the overall student experience is enhanced (Carvalho &
Mello, 2011).
The current system that is installed for incident reporting and management takes
several hours to resolve the student queries and inquiries. There are also numerous
days that go by without any action. This leads to the deterioration of the student
experience and engagement levels.
With the development and deployment of Sam Bot, the real-time handling and
resolution of the student queries will be done. This will be beneficial for the students
as well as for the administration.
Page 1
1.1 Purpose of this Document
The document is an analysis document for the Sam Bot project. Sam Bot is an online
chat system for students and the document includes the background details of the
project along with the information on the business goals, vision, stakeholders,
requirements, and delivery.
1.2 Scope of this document
The scope of the document is to cover the analysis details of the project to present the
information on the project background and goals along with the high-level details of
the project requirements, approach, stakeholders, and delivery.
The document will include the approach that will be used in the project followed by
the details of the primary stakeholders involved. The stakeholder definition and
communication will be included. The report will also cover the product vision in
terms of the vision statement and product road map. The requirements, project
delivery & review, and project management details will be covered as well.
1.3 Background
The project is Sam Bot which is an online-chat system being developed for the
students. The system will allow the students to place their queries and these will be
resolved by the administrator on a real-time basis. It is a chat bot that will be
developed and implemented to make sure that the overall turnaround time for query
resolution is reduced and the overall student experience is enhanced (Carvalho &
Mello, 2011).
The current system that is installed for incident reporting and management takes
several hours to resolve the student queries and inquiries. There are also numerous
days that go by without any action. This leads to the deterioration of the student
experience and engagement levels.
With the development and deployment of Sam Bot, the real-time handling and
resolution of the student queries will be done. This will be beneficial for the students
as well as for the administration.
Page 1
2 Business Goals
ï‚· Reduce the turnaround time for recording customer queries to less than a
minute.
ï‚· Enhance the student engagement and satisfaction levels by at least 70%.
ï‚· Improve the administration accuracy and query handling abilities by at least
75%.
ï‚· Carry out the real-time query recording and handling processes
Currently, the turnaround time involved in the system is huge which leads to the
reduction in the user engagement and connection levels. With the implementation of
Sam Bot, the users will be provided with the response to their specific queries in a
timeframe of less than one minute. The quick response to the queries and streamlining
of the processes will enhance the student engagement and satisfaction levels by 70%.
The automated query handling and incident management will be made possible which
will have a positive influence on the query handling mechanisms. The real-time and
automated handling of the processes will be enabled.
2.1 Agile Approach
The agile approach that will be used in the project will be Agile SCRUM. It is the
agile development methodology in which the system development will be carried out
using incremental and iterative approach. The customers will be provided with the
working products at the gap of two to four weeks. The approach has been selected for
this project there are several changes that may come up in the advanced stages of the
project. Also, these changes may be experienced in the other phases of the system.
With the use of the agile SCRUM approach, the Sam Bot system developed will be
extremely flexible in nature. The changes will be readily accepted (Mahnic, 2015).
The customer satisfaction levels will also be enhanced with the adoption of this
methodology. The end-users, that is, the students and the administrators will be
provided with the working set of products at regular and frequent intervals. There may
be several changes desired by these users and these changes will be immediately
reflected in the next working product. The level of customer engagement and
satisfaction will go up as a result.
The development work will be done in an iterative manner. The work products will
include the Sam Bot online-chat system with the implementation of varied
Page 2
ï‚· Reduce the turnaround time for recording customer queries to less than a
minute.
ï‚· Enhance the student engagement and satisfaction levels by at least 70%.
ï‚· Improve the administration accuracy and query handling abilities by at least
75%.
ï‚· Carry out the real-time query recording and handling processes
Currently, the turnaround time involved in the system is huge which leads to the
reduction in the user engagement and connection levels. With the implementation of
Sam Bot, the users will be provided with the response to their specific queries in a
timeframe of less than one minute. The quick response to the queries and streamlining
of the processes will enhance the student engagement and satisfaction levels by 70%.
The automated query handling and incident management will be made possible which
will have a positive influence on the query handling mechanisms. The real-time and
automated handling of the processes will be enabled.
2.1 Agile Approach
The agile approach that will be used in the project will be Agile SCRUM. It is the
agile development methodology in which the system development will be carried out
using incremental and iterative approach. The customers will be provided with the
working products at the gap of two to four weeks. The approach has been selected for
this project there are several changes that may come up in the advanced stages of the
project. Also, these changes may be experienced in the other phases of the system.
With the use of the agile SCRUM approach, the Sam Bot system developed will be
extremely flexible in nature. The changes will be readily accepted (Mahnic, 2015).
The customer satisfaction levels will also be enhanced with the adoption of this
methodology. The end-users, that is, the students and the administrators will be
provided with the working set of products at regular and frequent intervals. There may
be several changes desired by these users and these changes will be immediately
reflected in the next working product. The level of customer engagement and
satisfaction will go up as a result.
The development work will be done in an iterative manner. The work products will
include the Sam Bot online-chat system with the implementation of varied
Page 2
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
functionalities done in each of these iterations. The most relevant and must-have
functionalities will be developed and implemented in the initial phases. For instance,
the user interface, user profile & groups, etc. will be implemented in the initial
iterations. The subsequent iterations will involve the deployment of the other
functions (Adi, 2015). The system will provide the users to connect with the system in
an automated manner as the response time to any of the student queries will be
reduced to less than one minute.
3 Stakeholders
3.1 Stakeholder Definition
Stakeholder Description Interest Impact on
the
Product
Influence
Level
Contribution
Level
Project Sponsor The stakeholder will be
the project client for the
product being developed
and the funds will be
arranged and provided by
the stakeholder.
High High High High
Students and
Administrators
– End Users
The stakeholder group
will involve the end-users
that will utilize the
system and will make use
of the system features and
functionalities. The UAT
will also be conducted by
the stakeholder group.
High High High Moderate
Vendor Groups The tools and equipment
required by the project
team to design, develop,
and deploy the
application will be
Low Moderate Low High
Page 3
functionalities will be developed and implemented in the initial phases. For instance,
the user interface, user profile & groups, etc. will be implemented in the initial
iterations. The subsequent iterations will involve the deployment of the other
functions (Adi, 2015). The system will provide the users to connect with the system in
an automated manner as the response time to any of the student queries will be
reduced to less than one minute.
3 Stakeholders
3.1 Stakeholder Definition
Stakeholder Description Interest Impact on
the
Product
Influence
Level
Contribution
Level
Project Sponsor The stakeholder will be
the project client for the
product being developed
and the funds will be
arranged and provided by
the stakeholder.
High High High High
Students and
Administrators
– End Users
The stakeholder group
will involve the end-users
that will utilize the
system and will make use
of the system features and
functionalities. The UAT
will also be conducted by
the stakeholder group.
High High High Moderate
Vendor Groups The tools and equipment
required by the project
team to design, develop,
and deploy the
application will be
Low Moderate Low High
Page 3
performed by the
stakeholder.
Project Board The stakeholder will be
the authorizing body and
the mediator between the
client and the project
team.
Moderate High High Moderate
Project
Manager
The internal authority
will be on the stakeholder
and the stakeholder will
carry out project handling
and management
activities.
High High High High
Project Team The stakeholder group
will execute the project
tasks and activities to
develop and deploy the
intended system.
Moderate High Low High
3.2 Stakeholder Communication
The communication with the stakeholders will be facilitated by the Project Manager.
There will be communication guidelines and mechanisms included by the Project
Manager in the project communication plan. The communication with the internal
stakeholders will be regular and frequent as compared with the external stakeholders.
The internal stakeholders will meet every alternate day in the meeting room to discuss
the project updates and plan the further steps of action. There will be a daily stand-up
of the project team and manager to discuss the progress and issues. There will be use
of emails and instant messages to share the project details and information in a real-
time basis. There will also be use of SharePoint as document storage and sharing
medium.
Page 4
stakeholder.
Project Board The stakeholder will be
the authorizing body and
the mediator between the
client and the project
team.
Moderate High High Moderate
Project
Manager
The internal authority
will be on the stakeholder
and the stakeholder will
carry out project handling
and management
activities.
High High High High
Project Team The stakeholder group
will execute the project
tasks and activities to
develop and deploy the
intended system.
Moderate High Low High
3.2 Stakeholder Communication
The communication with the stakeholders will be facilitated by the Project Manager.
There will be communication guidelines and mechanisms included by the Project
Manager in the project communication plan. The communication with the internal
stakeholders will be regular and frequent as compared with the external stakeholders.
The internal stakeholders will meet every alternate day in the meeting room to discuss
the project updates and plan the further steps of action. There will be a daily stand-up
of the project team and manager to discuss the progress and issues. There will be use
of emails and instant messages to share the project details and information in a real-
time basis. There will also be use of SharePoint as document storage and sharing
medium.
Page 4
The external communications will be done on a weekly basis through a meeting
facilitated by the Project Manager. The meeting will take place on the tele-conference
medium. The secure documents and reports will be uploaded on the SharePoint
location of the project. The use of emails and instant messages will be done to
enhance the communication speed.
4 Product Vision
4.1 Vision Statement
For: Students, Administrators
Who: want a real-time online chat system
The Sam Bot is an online chat system
That: will reduce the turnaround time for query recording and handling
Unlike: Existing system that takes several hours or days for handling and responding
Our product: will enhance the user satisfaction and engagement levels.
4.2 Product Road Map
User Activities Login to the system, start chat, end chat
User Tasks System login, start chat, send query, attach files, end chat,
provide response, provide feedback
User Stories Release 1:
US1: As a student, I would like the ability to log in to the
system so that I may get access to the online chat facility.
US2: As an administrator, I would like the ability to log in to
the system so that I may get access to the online chat facility.
US3: As a student, I would like the ability to start a chat so
that I may put across my queries and complaints.
US4: As an administrator, I would like to have the ability to
receive a chat request from the student and respond to in less
than a minute to enhance the student engagement level
(Hudda, Mahajan & Chopra, 2016).
Page 5
facilitated by the Project Manager. The meeting will take place on the tele-conference
medium. The secure documents and reports will be uploaded on the SharePoint
location of the project. The use of emails and instant messages will be done to
enhance the communication speed.
4 Product Vision
4.1 Vision Statement
For: Students, Administrators
Who: want a real-time online chat system
The Sam Bot is an online chat system
That: will reduce the turnaround time for query recording and handling
Unlike: Existing system that takes several hours or days for handling and responding
Our product: will enhance the user satisfaction and engagement levels.
4.2 Product Road Map
User Activities Login to the system, start chat, end chat
User Tasks System login, start chat, send query, attach files, end chat,
provide response, provide feedback
User Stories Release 1:
US1: As a student, I would like the ability to log in to the
system so that I may get access to the online chat facility.
US2: As an administrator, I would like the ability to log in to
the system so that I may get access to the online chat facility.
US3: As a student, I would like the ability to start a chat so
that I may put across my queries and complaints.
US4: As an administrator, I would like to have the ability to
receive a chat request from the student and respond to in less
than a minute to enhance the student engagement level
(Hudda, Mahajan & Chopra, 2016).
Page 5
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Release 2:
US5: As a student, I would like the ability to attach and send
files to the admin during the chat so that the explanation of
the query is adequately done.
US6: As an administrator, I would like the ability to receive
the files sent by the student to understand the query.
US7: As a student, I would like the ability to end the chat so
that the session is completed.
US8: As an administrator, I would like to provide response to
the query or escalate the matter to the senior officials to make
sure that the student query is handled.
Release 3
US9: As a student, I would like the ability to provide the
feedback so that the improvement areas are worked upon.
US10: As an administrator, I would like the ability to receive
the feedback given by the student for further improvement.
5 Requirements
5.1 Story Mapping
User Sequence User Stories
Release 1
Student 1 US1
Administrator 2 US2
Student 3 US3
Administrator 4 US4
Release 2:
Student 5 US5
Page 6
US5: As a student, I would like the ability to attach and send
files to the admin during the chat so that the explanation of
the query is adequately done.
US6: As an administrator, I would like the ability to receive
the files sent by the student to understand the query.
US7: As a student, I would like the ability to end the chat so
that the session is completed.
US8: As an administrator, I would like to provide response to
the query or escalate the matter to the senior officials to make
sure that the student query is handled.
Release 3
US9: As a student, I would like the ability to provide the
feedback so that the improvement areas are worked upon.
US10: As an administrator, I would like the ability to receive
the feedback given by the student for further improvement.
5 Requirements
5.1 Story Mapping
User Sequence User Stories
Release 1
Student 1 US1
Administrator 2 US2
Student 3 US3
Administrator 4 US4
Release 2:
Student 5 US5
Page 6
Administrator 6 US6
Student 8 US7
Administrator 7 US8
Release 3
Student 9 US9
Administrator 10 US10
5.2 Story Decomposition
Original User Stories
Release 1
Decomposed User Stories
Release 1
As a student, I would like the ability to log in to
the system so that I may get access to the online
chat facility.
As a student, I would like the
ability to log in to the system so
that I may get access to the online
chat facility.
As an administrator, I would like the ability to
log in to the system so that I may get access to
the online chat facility.
As an administrator, I would like
the ability to log in to the system
so that I may get access to the
online chat facility.
As a student, I would like the ability to start a
chat so that I may put across my queries and
complaints.
As a student, I would like the
ability to start a chat so that I may
put across my queries.
As a student, I would like the
ability to start a chat so that I may
put across the feedback and
updates
As an administrator, I would like to have the
ability to receive a chat request from the student
As an administrator, I would like
to have the ability to receive a chat
Page 7
Student 8 US7
Administrator 7 US8
Release 3
Student 9 US9
Administrator 10 US10
5.2 Story Decomposition
Original User Stories
Release 1
Decomposed User Stories
Release 1
As a student, I would like the ability to log in to
the system so that I may get access to the online
chat facility.
As a student, I would like the
ability to log in to the system so
that I may get access to the online
chat facility.
As an administrator, I would like the ability to
log in to the system so that I may get access to
the online chat facility.
As an administrator, I would like
the ability to log in to the system
so that I may get access to the
online chat facility.
As a student, I would like the ability to start a
chat so that I may put across my queries and
complaints.
As a student, I would like the
ability to start a chat so that I may
put across my queries.
As a student, I would like the
ability to start a chat so that I may
put across the feedback and
updates
As an administrator, I would like to have the
ability to receive a chat request from the student
As an administrator, I would like
to have the ability to receive a chat
Page 7
and respond to in less than a minute to enhance
the student engagement level.
request from the student to provide
a response.
As an administrator, I would like
to have the ability to respond to the
query in less than a minute to
enhance the student engagement
level (Memmel & Obendorf,
2010).
Release 2: Release 2:
As a student, I would like the ability to attach
and send files to the admin during the chat so
that the explanation of the query is adequately
done.
As a student, I would like the
ability to attach files to the admin
during the chat so that the
explanation of the query is
adequately done.
As a student, I would like the
ability to send files to the admin
during the chat so that the
explanation of the query is
adequately done.
As an administrator, I would like the ability to
receive the files sent by the student to
understand the query.
As an administrator, I would like
the ability to receive the files sent
by the student to understand the
query.
As a student, I would like the ability to end the
chat so that the session is completed.
As a student, I would like the
ability to end the chat so that the
session is completed.
As an administrator, I would like to provide
response to the query or escalate the matter to
the senior officials to make sure that the student
query is handled.
As an administrator, I would like
to provide response to the query to
make sure that the student query is
handled.
As an administrator, I would like
to escalate the matter to the senior
Page 8
the student engagement level.
request from the student to provide
a response.
As an administrator, I would like
to have the ability to respond to the
query in less than a minute to
enhance the student engagement
level (Memmel & Obendorf,
2010).
Release 2: Release 2:
As a student, I would like the ability to attach
and send files to the admin during the chat so
that the explanation of the query is adequately
done.
As a student, I would like the
ability to attach files to the admin
during the chat so that the
explanation of the query is
adequately done.
As a student, I would like the
ability to send files to the admin
during the chat so that the
explanation of the query is
adequately done.
As an administrator, I would like the ability to
receive the files sent by the student to
understand the query.
As an administrator, I would like
the ability to receive the files sent
by the student to understand the
query.
As a student, I would like the ability to end the
chat so that the session is completed.
As a student, I would like the
ability to end the chat so that the
session is completed.
As an administrator, I would like to provide
response to the query or escalate the matter to
the senior officials to make sure that the student
query is handled.
As an administrator, I would like
to provide response to the query to
make sure that the student query is
handled.
As an administrator, I would like
to escalate the matter to the senior
Page 8
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
officials in case of absence of
authority to solve the matters on
my own to make sure that the
student query is handled.
Release 3 Release 3
As a student, I would like the ability to provide
the feedback so that the improvement areas are
worked upon.
As a student, I would like the
ability to provide the feedback so
that the improvement areas are
worked upon.
As an administrator, I would like the ability to
receive the feedback given by the student for
further improvement.
As an administrator, I would like
the ability to receive the feedback
given by the student for further
improvement.
6 Delivery and Review
The requirements will be maintained and developed using the Product Backlog and
the working sets will be extracted from this backlog at regular intervals.
At the end of every sprint, there will be a working product shared with the end system
users. These users will perform the acceptance testing on the working product
delivered and the comments provided will be recorded. The set of changes will be
identified from the user response. The inclusion of the response will be done in the
next sprint. In this manner, the user expectations will be included in the final system
that will be delivered. Also, the overall user experience levels will be high.
The use of SCRUM methodology will be done along with the use of the tools as Agilo
for Scrum and Pivotal Tracker (Kautz, Johanson & Uldahl, 2014). These tools will
make sure that the incorporation of the user stories is effectively done and higher level
of customer collaboration is achieved.
Page 9
authority to solve the matters on
my own to make sure that the
student query is handled.
Release 3 Release 3
As a student, I would like the ability to provide
the feedback so that the improvement areas are
worked upon.
As a student, I would like the
ability to provide the feedback so
that the improvement areas are
worked upon.
As an administrator, I would like the ability to
receive the feedback given by the student for
further improvement.
As an administrator, I would like
the ability to receive the feedback
given by the student for further
improvement.
6 Delivery and Review
The requirements will be maintained and developed using the Product Backlog and
the working sets will be extracted from this backlog at regular intervals.
At the end of every sprint, there will be a working product shared with the end system
users. These users will perform the acceptance testing on the working product
delivered and the comments provided will be recorded. The set of changes will be
identified from the user response. The inclusion of the response will be done in the
next sprint. In this manner, the user expectations will be included in the final system
that will be delivered. Also, the overall user experience levels will be high.
The use of SCRUM methodology will be done along with the use of the tools as Agilo
for Scrum and Pivotal Tracker (Kautz, Johanson & Uldahl, 2014). These tools will
make sure that the incorporation of the user stories is effectively done and higher level
of customer collaboration is achieved.
Page 9
7 Project Management
Agile methodology for project management will be used to manage the project tasks
and activities. The methodology will provide an ad-hoc method for managing all the
project tasks and activities (Rajasekaran, 2015). There will be use of several agile
tools and mechanisms to make sure that the management is adequately done.
The methodology will be adaptive in nature and there will no pre-defined plans put in
place. The planning and analysis will be done in an ad-hoc manner with the ability to
the project management and team to carry out risk management, change management,
stakeholder management, and communication management in an integrated manner.
The tracking and management of the schedule and costs will also be done in the same
process.
7.1 APM Framework
Vision Speculate Explore Launch Closing
Project Vision
Project
Requirements
Project Scope
Feasibility
Evaluation
Story Plan
Management
Plan
Estimations
Stakeholders
Development
Tools
Iterative
Delivery
User Acceptance
Testing
Final QA
Documentation
Feedback
Closure Report
Page 10
Agile methodology for project management will be used to manage the project tasks
and activities. The methodology will provide an ad-hoc method for managing all the
project tasks and activities (Rajasekaran, 2015). There will be use of several agile
tools and mechanisms to make sure that the management is adequately done.
The methodology will be adaptive in nature and there will no pre-defined plans put in
place. The planning and analysis will be done in an ad-hoc manner with the ability to
the project management and team to carry out risk management, change management,
stakeholder management, and communication management in an integrated manner.
The tracking and management of the schedule and costs will also be done in the same
process.
7.1 APM Framework
Vision Speculate Explore Launch Closing
Project Vision
Project
Requirements
Project Scope
Feasibility
Evaluation
Story Plan
Management
Plan
Estimations
Stakeholders
Development
Tools
Iterative
Delivery
User Acceptance
Testing
Final QA
Documentation
Feedback
Closure Report
Page 10
8 References
Adi, P. (2015). Scrum Method Implementation in a Software Development Project
Management. International Journal Of Advanced Computer Science And
Applications, 6(9). doi: 10.14569/ijacsa.2015.060927
Carvalho, B., & Mello, C. (2011). Scrum agile product development method -
literature review, analysis and classification. Product Management &
Development, 9(1), 39-49. doi: 10.4322/pmd.2011.005
Hudda, S., Mahajan, R., & Chopra, S. (2016). Prioritization of User-Stories in Agile
Environment. Indian Journal Of Science And Technology, 9(45). doi:
10.17485/ijst/2016/v9i45/105069
Kautz, K., Johanson, T., & Uldahl, A. (2014). The Perceived Impact of the Agile
Development and Project Management Method Scrum on Information
Systems and Software Development Productivity. Australasian Journal Of
Information Systems, 18(3). doi: 10.3127/ajis.v18i3.1095
Mahnic, V. (2012). A Capstone Course on Agile Software Development Using
Scrum. IEEE Transactions On Education, 55(1), 99-106. doi:
10.1109/te.2011.2142311
Memmel, T., & Obendorf, H. (2010). Agile + Usability. Agile Methoden, Usability
Engineering, User Experience, User-Centered Design. I-Com, 9(1). doi:
10.1524/icom.2010.0008
Rajasekaran, V. (2015). Issues in Scrum Agile Development Principles and Practices
in software development. Indian Journal Of Science And Technology, 8(35).
doi: 10.17485/ijst/2015/v8i35/79037
Page 11
Adi, P. (2015). Scrum Method Implementation in a Software Development Project
Management. International Journal Of Advanced Computer Science And
Applications, 6(9). doi: 10.14569/ijacsa.2015.060927
Carvalho, B., & Mello, C. (2011). Scrum agile product development method -
literature review, analysis and classification. Product Management &
Development, 9(1), 39-49. doi: 10.4322/pmd.2011.005
Hudda, S., Mahajan, R., & Chopra, S. (2016). Prioritization of User-Stories in Agile
Environment. Indian Journal Of Science And Technology, 9(45). doi:
10.17485/ijst/2016/v9i45/105069
Kautz, K., Johanson, T., & Uldahl, A. (2014). The Perceived Impact of the Agile
Development and Project Management Method Scrum on Information
Systems and Software Development Productivity. Australasian Journal Of
Information Systems, 18(3). doi: 10.3127/ajis.v18i3.1095
Mahnic, V. (2012). A Capstone Course on Agile Software Development Using
Scrum. IEEE Transactions On Education, 55(1), 99-106. doi:
10.1109/te.2011.2142311
Memmel, T., & Obendorf, H. (2010). Agile + Usability. Agile Methoden, Usability
Engineering, User Experience, User-Centered Design. I-Com, 9(1). doi:
10.1524/icom.2010.0008
Rajasekaran, V. (2015). Issues in Scrum Agile Development Principles and Practices
in software development. Indian Journal Of Science And Technology, 8(35).
doi: 10.17485/ijst/2015/v8i35/79037
Page 11
1 out of 13
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024  |  Zucol Services PVT LTD  |  All rights reserved.