SIT764 - Agile and SDLC: Individual Task 2.1, Mobile App Project
VerifiedAdded on 2022/09/12
|7
|1206
|26
Homework Assignment
AI Summary
This assignment analyzes the application of Agile and SDLC methodologies in the context of a mobile app development project. The student outlines the main activities involved in managing such a project, emphasizing the Agile method as the most suitable approach. The assignment includes two user stories based on a given scenario, identifies the appropriate Scrum role (Scrum master), and assesses a truck factor risk associated with the project. Additionally, it explores factors that contribute to successful and unsuccessful teamwork, providing insights into project management best practices. The student references relevant literature to support their analysis, demonstrating an understanding of the concepts discussed.

Running head: AGILE AND SDLC
Individual Pass Task 2.1: Agile and SDLC
Name of the Student:
Name of the University:
Individual Pass Task 2.1: Agile and SDLC
Name of the Student:
Name of the University:
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

1AGILE AND SDLC
Table of Contents
1. Main activities involved to manage mobile app development project...............................2
2. Best method used for mobile app development project......................................................2
3. Two user stories..................................................................................................................3
4. Suitable Scrum role.............................................................................................................3
5. Truck factor risk associated with the project......................................................................3
6. Factors lead to successful teamwork and bad teamwork....................................................4
References..................................................................................................................................5
Table of Contents
1. Main activities involved to manage mobile app development project...............................2
2. Best method used for mobile app development project......................................................2
3. Two user stories..................................................................................................................3
4. Suitable Scrum role.............................................................................................................3
5. Truck factor risk associated with the project......................................................................3
6. Factors lead to successful teamwork and bad teamwork....................................................4
References..................................................................................................................................5

2AGILE AND SDLC
1. Main activities involved to manage mobile app development project
Plan: The agile sprint is started with meeting for sprint planning, when the project
team members are coming together to lay out for the project components. The project
manager is being prioritized with the project work from backlog of the project tasks to assign
it to the project team.
Develop: The product is to be developed as well as designed in accordance with
approved project guidelines (Harned 2018).
Testing: There is performing of completed project testing as well as documentation
before project delivery.
Delivery: There is presenting of working product as well as software to the project
stakeholders as well as customers.
Assess: There is taking of feedback from the customers as well as stakeholders and
then gathering the information to incorporate in next sprint (Peroni 2016).
2. Best method used for mobile app development project
Agile method is the best method used for this mobile app development project. The
agile methodology is a process through which the project team can able to manage the project
by breaking down in various project stages. This project management methodology helps to
save the project time as well as money along with reduces the project documentation. It is
adaptable to the project changes and also provides with regular project feedback from end of
the project users (Baham et al. 2017). One of the key benefit of this method is in adaptability.
Agile project team can react to the project changes by reducing the project risks lead to
complete project failure.
1. Main activities involved to manage mobile app development project
Plan: The agile sprint is started with meeting for sprint planning, when the project
team members are coming together to lay out for the project components. The project
manager is being prioritized with the project work from backlog of the project tasks to assign
it to the project team.
Develop: The product is to be developed as well as designed in accordance with
approved project guidelines (Harned 2018).
Testing: There is performing of completed project testing as well as documentation
before project delivery.
Delivery: There is presenting of working product as well as software to the project
stakeholders as well as customers.
Assess: There is taking of feedback from the customers as well as stakeholders and
then gathering the information to incorporate in next sprint (Peroni 2016).
2. Best method used for mobile app development project
Agile method is the best method used for this mobile app development project. The
agile methodology is a process through which the project team can able to manage the project
by breaking down in various project stages. This project management methodology helps to
save the project time as well as money along with reduces the project documentation. It is
adaptable to the project changes and also provides with regular project feedback from end of
the project users (Baham et al. 2017). One of the key benefit of this method is in adaptability.
Agile project team can react to the project changes by reducing the project risks lead to
complete project failure.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3AGILE AND SDLC
3. Two user stories
Based on the email, the two user stories are as follows:
As a user, I can go through meal menu so that I can get the dieting list for my weight
loss.
As a user, I can specify the exercises of losing weight so that I can choose most
suitable option for me.
4. Suitable Scrum role
Scrum master is the suitable scrum role for this project. As a scrum master, I will
be the facilitator of the agile development team. It is the methodology which allows the
project team to organize as well as make changes in accordance to the agile project
principles. The scrum master manages the agile process of how the information is to be
exchanged among the project team members. The scrum master is responsible to monitor
the scrum processes as well as project team meetings (Schmitz, Mahapatra and Nerur
2018). There is an increase in efficiency of the project team and motivate the project team
to meet with project quality as well as timeline.
5. Truck factor risk associated with the project
Based on the scenario, an idea is taken to have the project team with lot of
experience in the mobile app development and some of the members are good at
programming. As the project goal is to build a weight loss mobile application that has not
build before, training as well as staff education is required at all expertise. As all the
project team members are not equally knowledgeable, therefore it is a trick factor risk. In
order to mitigate this risk, the company should go for three bricks approach, where there
3. Two user stories
Based on the email, the two user stories are as follows:
As a user, I can go through meal menu so that I can get the dieting list for my weight
loss.
As a user, I can specify the exercises of losing weight so that I can choose most
suitable option for me.
4. Suitable Scrum role
Scrum master is the suitable scrum role for this project. As a scrum master, I will
be the facilitator of the agile development team. It is the methodology which allows the
project team to organize as well as make changes in accordance to the agile project
principles. The scrum master manages the agile process of how the information is to be
exchanged among the project team members. The scrum master is responsible to monitor
the scrum processes as well as project team meetings (Schmitz, Mahapatra and Nerur
2018). There is an increase in efficiency of the project team and motivate the project team
to meet with project quality as well as timeline.
5. Truck factor risk associated with the project
Based on the scenario, an idea is taken to have the project team with lot of
experience in the mobile app development and some of the members are good at
programming. As the project goal is to build a weight loss mobile application that has not
build before, training as well as staff education is required at all expertise. As all the
project team members are not equally knowledgeable, therefore it is a trick factor risk. In
order to mitigate this risk, the company should go for three bricks approach, where there
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4AGILE AND SDLC
is using of rule of thumb to distribute the knowledge about areas of expertise (Judd and
Blair 2019). It is a way to manage expertise on the new technologies.
6. Factors lead to successful teamwork and bad teamwork
Following are three factors lead to successful teamwork are:
I. Commitment: The team members understand their own work to fit
with the corporate project objectives as well as agree with the project
goals.
II. Communication: For the project group, communication helps in
knowing as well as respecting each of the project team members. The
team members should take care of each other’s suggestions and ideas
so that no one is hurt from anyone’s comments (Imran et al. 2019).
III. Conflict management: Each of the project team helps each other to
perform their work and respect each other’s suggestions, therefore
there is no conflicts occurred among the project group (Lindsjørn et al.
2016).
Confidence is one of the factor which lead to bad teamwork as all the project team
members are not confident in their skills and knowledge (Talman 2018). The project team
members are working well in the project while they have no confidence and no positive
attitude towards the business organization to meet with project goals.
is using of rule of thumb to distribute the knowledge about areas of expertise (Judd and
Blair 2019). It is a way to manage expertise on the new technologies.
6. Factors lead to successful teamwork and bad teamwork
Following are three factors lead to successful teamwork are:
I. Commitment: The team members understand their own work to fit
with the corporate project objectives as well as agree with the project
goals.
II. Communication: For the project group, communication helps in
knowing as well as respecting each of the project team members. The
team members should take care of each other’s suggestions and ideas
so that no one is hurt from anyone’s comments (Imran et al. 2019).
III. Conflict management: Each of the project team helps each other to
perform their work and respect each other’s suggestions, therefore
there is no conflicts occurred among the project group (Lindsjørn et al.
2016).
Confidence is one of the factor which lead to bad teamwork as all the project team
members are not confident in their skills and knowledge (Talman 2018). The project team
members are working well in the project while they have no confidence and no positive
attitude towards the business organization to meet with project goals.

5AGILE AND SDLC
References
Baham, C., Hirschheim, R., Calderon, A.A. and Kisekka, V., 2017. An agile methodology for
the disaster recovery of information systems under catastrophic scenarios. Journal of
Management Information Systems, 34(3), pp.633-663.
Harned, D., 2018. Hands-On Agile Software Development with JIRA: Design and manage
software projects using the Agile methodology. Packt Publishing Ltd.
Imran, S.M.J.I., Nawaz, M.S., Siddiqui, S.H. and Kashif, M., 2019. Does Project Teamwork
Matter? Investigating the Relationship between Transformational Leadership and Project
Success. Journal of Management Sciences, 6(1), pp.79-95.
Judd, M.M. and Blair, H.C., 2019. Leveraging Agile Methodology to Transform a University
Learning and Teaching Unit. In Agile and Lean Concepts for Teaching and Learning (pp.
171-185). Springer, Singapore.
Lindsjørn, Y., Sjøberg, D.I., Dingsøyr, T., Bergersen, G.R. and Dybå, T., 2016. Teamwork
quality and project success in software development: A survey of agile development
teams. Journal of Systems and Software, 122, pp.274-286.
Peroni, S., 2016. A simplified agile methodology for ontology development. In OWL:
Experiences and Directions–Reasoner Evaluation (pp. 55-69). Springer, Cham.
Schmitz, K., Mahapatra, R. and Nerur, S., 2018. User engagement in the era of hybrid agile
methodology. IEEE Software, 36(4), pp.32-40.
Talman, J., 2018, August. Enhancing Teamwork in Group Projects by Applying Principles of
Project Management. In Innovations in Teaching & Learning Conference Proceedings (Vol.
10).
References
Baham, C., Hirschheim, R., Calderon, A.A. and Kisekka, V., 2017. An agile methodology for
the disaster recovery of information systems under catastrophic scenarios. Journal of
Management Information Systems, 34(3), pp.633-663.
Harned, D., 2018. Hands-On Agile Software Development with JIRA: Design and manage
software projects using the Agile methodology. Packt Publishing Ltd.
Imran, S.M.J.I., Nawaz, M.S., Siddiqui, S.H. and Kashif, M., 2019. Does Project Teamwork
Matter? Investigating the Relationship between Transformational Leadership and Project
Success. Journal of Management Sciences, 6(1), pp.79-95.
Judd, M.M. and Blair, H.C., 2019. Leveraging Agile Methodology to Transform a University
Learning and Teaching Unit. In Agile and Lean Concepts for Teaching and Learning (pp.
171-185). Springer, Singapore.
Lindsjørn, Y., Sjøberg, D.I., Dingsøyr, T., Bergersen, G.R. and Dybå, T., 2016. Teamwork
quality and project success in software development: A survey of agile development
teams. Journal of Systems and Software, 122, pp.274-286.
Peroni, S., 2016. A simplified agile methodology for ontology development. In OWL:
Experiences and Directions–Reasoner Evaluation (pp. 55-69). Springer, Cham.
Schmitz, K., Mahapatra, R. and Nerur, S., 2018. User engagement in the era of hybrid agile
methodology. IEEE Software, 36(4), pp.32-40.
Talman, J., 2018, August. Enhancing Teamwork in Group Projects by Applying Principles of
Project Management. In Innovations in Teaching & Learning Conference Proceedings (Vol.
10).
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

6AGILE AND SDLC
1 out of 7
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
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.