Ist 621 Advanced Systems Analysis And Design Spring 2021 Cleveland ✓ Solved

IST 621 – Advanced Systems Analysis and Design Spring 2021, Cleveland State University Dr. Abdullah Oguz Individual Term Project INDIVIDUAL TERM PROJECT During this course, you will work on a project on an individual basis. You will examine an agile Information System (IS) project management approach (methods and frameworks) to improve your knowledge and to utilize in your job search and career. You should choose one of the agile approaches below: 1. Scrum 2.

Kanban 3. Scrumban 4. Extreme Programming (XP) 5. Crystal Methods 6. Feature-Driven Development (FDD) 7.

Dynamic Systems Development Model (DSDM) 8. Agile Unified Process 9. Scaling Frameworks a. Scrum of Scrums b. Scaled Agile Framework c.

Large Scale Scrum (LeSS) d. Enterprise Scrum e. Disciplined Agile (DA) IST 621 – Advanced Systems Analysis and Design Spring 2021, Cleveland State University Dr. Abdullah Oguz Individual Term Project The structure of the final paper should be as follows: 1. Introduction 2.

Characteristics of the agile PM approach that you chose a. Principles, artifacts, tools, methods b. Role of project team members and stakeholders c. Life cycle d. How it is used in systems analysis and design (SDLC and OOAD) e.

Possibility of blending the approach you chose with other agile aproaches (if applicable) 3. A real-world case study a. A short introduction b. Utilization of the agile approach 4. Critique of the agile approach based on the real-world case a.

Advantages of the method b. Disadvantages of the method and how to deal with the challenges 5. Conclusion 6. References IST 621 – Advanced Systems Analysis and Design Spring 2021, Cleveland State University Dr. Abdullah Oguz Individual Term Project Resources for Case Studies1 • • • scrumban//ch01.html#scrumban_case_study • revolution//app01.html#app01lev1sec6 • • • • • explained//ch07.html • • =19 • • • • • 1 You can also use case studies which have not been indicated in this list.

IST 621 – Advanced Systems Analysis and Design Spring 2021, Cleveland State University Dr. Abdullah Oguz Individual Term Project This assignment has three phases as displayed in the table below. Individual Term Project Phases Due Date Points 1. Proposal Feb . Interim report Mar .

Final submission Apr 29 175 TOTAL 250 • In the Proposal phase, you should explain why you chose that particular agile approach, and why you think that investigating this approach would benefit you. The proposal will be minimum 1 (one) page. • Interim report will include a summary of the case study you chose, and how it is related to the agile approach you are examining. This report will be minimum 1 (one) page. • The final submission will have minimum 6 (six) full pages in length excluding the title page and references. There won’t be an abstract section in any of the submissions. This assignment (proposal, interim report, and final submission) must be typed in a Microsoft Word document with 12 pt.

Times New Roman font. The text must be double-spaced on standard-sized paper (8.5" by 11") with 1" margins on all sides. References (including the in- text citations) should be documented using the guidelines provided in the following publication: IST 621 – Advanced Systems Analysis and Design Spring 2021, Cleveland State University Dr. Abdullah Oguz Individual Term Project â— American Psychological Association (2009). Publication Manual of the American Psychological Association.

Sixth edition. Washington, DC: American Psychological Association. You can use the following website to review a good example for using references in this format: The originality of your final paper will be assessed on Blackboard with SafeAssign originality reports. You will work on this assignment on an individual basis (not in groups and teams). Individuals should neither seek nor receive help from anyone including classmates, friends and family members in completing this assignment.

If there is a strong evidence that your assignment is the same with another classmate’s assignment, your score will be zero. There will NOT be any make-up assignment for this failed assignment.

Paper for above instructions

Introduction

In the landscape of software development and information systems, agility is essential for adaptability and responsiveness. Agile methodologies have gained popularity for their iterative approaches to project management, promoting flexibility, continuous improvement, and high customer satisfaction. Among various agile frameworks, Scrum stands out for its structured yet adaptable execution. This paper analyzes the characteristics of Scrum, discusses its implementation in real-world scenarios, critiques its effectiveness, and concludes with insights on its strengths and weaknesses as an agile project management approach.

Characteristics of Scrum

Principles, Artifacts, Tools, and Methods

Scrum is grounded in the Agile Manifesto, emphasizing interactions, working software, and customer collaboration. The framework consists of key artifacts: the Product Backlog, a prioritized list of features; the Sprint Backlog, a list of tasks for an individual sprint; and the Increment, the completed work at the end of each sprint (Schwaber & Sutherland, 2020). Tools such as burndown charts, task boards, and scrum software (e.g., Jira, Trello) facilitate transparency and team collaboration (Schmidt et al., 2019).
In methodology, Scrum implements fixed-length iterations called sprints, which typically last two to four weeks. Each sprint begins with a Sprint Planning Meeting and ends with a Sprint Review and Retrospective to reflect on what worked well and what could improve (Sutherland, 2014).

Role of Project Team Members and Stakeholders

The Scrum Team comprises specific roles including:
- Product Owner: Represents stakeholders, manages the Product Backlog, and clarifies requirements (Cohn, 2010).
- Scrum Master: Facilitates the Scrum process, removes impediments, and ensures that agile principles are followed (Schwaber, 2004).
- Development Team: Consists of self-organizing, cross-functional members who are responsible for delivering the product increment (Scrum Alliance, 2020).
Stakeholders engage throughout the process, providing feedback during sprint reviews to ensure alignment with business goals (Whittaker, 2016).

Life Cycle

Scrum follows a cyclic life cycle encompassing:
1. Sprint Planning: Define sprint goals and tasks.
2. Execution: Daily stand-ups and collaborative work to complete tasks.
3. Sprint Review: Present the increment and gather feedback.
4. Sprint Retrospective: Reflect on the sprint to identify areas for improvement.
This cycle continues until the product is sufficiently developed or project goals are met (Sutherland, 2014).

Systems Analysis and Design (SDLC and OOAD)

The Scrum framework can be adapted for Systems Development Life Cycle (SDLC) and Object-Oriented Analysis and Design (OOAD). In SDLC, Scrum enables rapid iterations that refine software features based on user feedback, enhancing quality (Sutherland & Schwaber, 2017). Meanwhile, OOAD principles, such as use case modeling, can assist Product Owners in defining user stories that capture functional requirements succinctly.

Blending with Other Agile Approaches

Scrum can be blended with practices from Kanban (Scrumban), enhancing flow by limiting work in progress and focusing on continuous delivery (LADAS, 2009). Such integration helps teams optimize efficiency while upholding Scrum's core principles.

A Real-World Case Study: Spotify

Introduction

Spotify, the music streaming giant, adopted the Scrum framework to enhance its agile development processes. The company emphasizes a culture of collaboration and innovation, using Scrum to manage thousands of engineers across various teams (Kniberg & Ivarsson, 2012).

Utilization of the Agile Approach

Spotify's implementation of Scrum is reflected in its "Squads, Tribes, Chapters, and Guilds" structure. Each squad functions like a mini-Scrum team, managing its backlog and working autonomously towards common goals (Kniberg & Ivarsson, 2012). Frequent feedback loops and collaborative retrospectives ensure responsiveness to user needs and alignment with the company's agile culture.

Critique of the Agile Approach

Advantages of Scrum

Scrum offers numerous advantages, such as:
1. Flexibility: The framework accommodates changes swiftly, allowing teams to pivot based on feedback (Schwaber, 2004).
2. Enhanced Collaboration: Daily stand-ups foster communication and synergy within teams (Sutherland, 2014).
3. Results-Oriented: Regular increments ensure that value is consistently delivered to stakeholders (Schmidt et al., 2019).

Disadvantages of Scrum

Despite its strengths, Scrum faces challenges:
1. Implementation Difficulty: Organizations often struggle to adopt Scrum fully, leading to pseudo-Scrum practices that undercut effectiveness (Schwaber, 2004).
2. Role Clarity: Misunderstandings about team roles can lead to conflicts or unanticipated challenges (Cohn, 2010).
3. Scaling Issues: When trying to implement Scrum across larger teams or organizations, maintaining alignment and coordination can be problematic (Sutherland & Schwaber, 2017).
To address these challenges, organizations should invest in robust training, designate experienced Scrum Masters, and regularly evaluate the Scrum process for misapplications.

Conclusion

Scrum serves as a powerful agile project management framework that emphasizes interaction, customer collaboration, and iterative delivery. As demonstrated by the Spotify case study, Scrum allows organizations to remain adaptable in a fast-paced environment while fostering a culture of continuous improvement. While Scrum is not void of challenges, including improper implementations and scaling difficulties, its advantages like remarkable flexibility and results-oriented practices position it as a leading choice for project management in the agile realm. By investing in people and processes, organizations can maximize the potential of Scrum to drive project success.

References

1. Cohn, M. (2010). User Stories Applied: For Agile Software Development. Addison-Wesley.
2. Kniberg, H., & Ivarsson, A. (2012). Scaling Agile@Spotify with Tribes, Squads, Chapters, and Guilds. Available at https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyEngineeringCulture.pdf.
3. LADAS, C. (2009). Scrumban: Essays on Kanban Systems for Lean Software Development. Modus Cooperandi Press.
4. Schmidt, D., Mazzara, M., & Gunter, C. (2019). Agile Software Architecture. Springer.
5. Schwaber, K. (2004). Agile Project Management with Scrum. Microsoft Press.
6. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Available at https://scrumguides.org/scrum-guide.html.
7. Sutherland, J. (2014). Scrum: The Art of Doing Twice the Work in Half the Time. Crown Business.
8. Sutherland, J., & Schwaber, K. (2017). The Scrum Guide™ 2017. Scrum.org.
9. Scrum Alliance. (2020). Scrum Guide. Available at https://www.scrumalliance.org/learn-about-scrum.
10. Whittaker, B. (2016). Agile Coach: How to Be a Great Scrum Master. Available at https://www.agilecoach.com.