Scribd
Upload
4 views4 pages

Atern and Scrum: Agile Methodologies Explained

Uploaded by

Rahul
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views4 pages

Atern and Scrum: Agile Methodologies Explained

Uploaded by

Rahul
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Spm Unit 2

Q) What is Atern /Dynamic Systems Development method ? What are its eight core
priciples.

Atern, or Dynamic Systems Development Method (DSDM), is an Agile project management


method developed in 1994 to bring structure and discipline to Agile projects. It ensures that
business needs are met through timely, collaborative, and high-quality project delivery.

The Eight Core Principles of Atern:


1. Focus on Business Need: Every decision is made with the business need in mind, ensuring
that each project step is valuable and meets real business requirements.
2. Deliver on Time: Using time-boxing, Atern emphasizes timely delivery to meet deadlines,
delivering valuable results even if less essential elements are postponed.
3. Collaborate: Atern promotes a collaborative, one-team culture where users and stakeholders
work closely with the development team to ensure shared understanding.
4. Never Compromise Quality: Quality standards are set from the beginning, and frequent
testing throughout the project ensures these standards are met without compromise.
5. Develop Iteratively: Atern uses an iterative approach, allowing for feedback and changes in
each cycle, which helps improve the project over time.
6. Build Incrementally from Firm Foundations: Projects are built in small, incremental
stages on a strong foundation, allowing flexibility and growth in each phase.
7. Communicate Continuously: Continuous communication with stakeholders ensures clarity
and alignment, often through workshops and regular updates.
8. Demonstrate Control: Using clear plans and progress reports, Atern keeps stakeholders
informed, ensuring project transparency and control.

Q) What do you understand by the term 'ceremonies' in a scrum project? Explain the
different types of ceremonies that are observed in a Scrum project and their
significance

Scrum is an Agile framework used for developing and sustaining complex products. It was created
by Ken Schwaber and Jeff Sutherland and is widely applied in software development, hardware,
embedded systems, and more. Scrum is lightweight, simple to understand, but difficult to master. It
focuses on teamwork, flexibility, and continuous improvement through sprints, which are short
cycles of work that typically last no more than two weeks.
Scrum is based on three key pillars: transparency, inspection, and adaptation. It organizes work into
roles, ceremonies, and artifacts to ensure clear communication and efficient progress towards
goals.
OR
Scrum is an Agile framework used for developing complex products through teamwork,
transparency, and continuous improvement. It divides work into sprints—short, fixed iterations,
typically lasting 2 weeks

Ceremonies in Scrum:
Scrum Ceremonies are specific meetings that structure the Scrum process, helping teams plan,
review, and improve their work.
1. Sprint Planning:
The team plans what to work on in the upcoming sprint and how to accomplish it. This
ensures clear goals and shared commitment.
2. Daily Scrum:
A 15-minute meeting where team members discuss what they did, what they will do, and
any obstacles. It ensures daily synchronization and transparency.
3. Sprint Review:
At the end of the sprint, the team demonstrates the completed work to stakeholders for
feedback, ensuring alignment with business needs.
4. Sprint Retrospective:
The team reflects on the sprint, identifying what went well, what didn’t, and what can be
improved for the next sprint. This fosters continuous improvement.

Significance of Scrum Ceremonies:


These ceremonies help maintain focus, align the team with goals, and improve processes. They
ensure the team is working on the right tasks, communicating effectively, and always improving
their workflow.

Q) Explain the five major components of Albrecht Function Point Analysis.

External Input (EI):


• These are input transactions that update internal computer files. For example, this is when
data from a user or an external source is entered into the system.
• External Output (EO):
• These are transactions that extract and display data from internal computer files, like
creating reports or output screens. They process and show data to the user.
• External Inquiry (EQ):
• These are user-initiated transactions that provide information but do not update files.
Typically, the user enters data to get the information they need.
• Logical Interface File (LIF):
• This is like a data store within the system, created and accessed by the system itself. It
serves as the main source of data for the system.
• External Interface File (EIF):
• This is a data store maintained by a different application but is accessed by the system for
reference or data retrieval.

Q) What are the advantages and disadvantages of a Spiral model?

The Spiral Model is an iterative software development model similar to the incremental model but
with more emphasis on risk analysis. This model is divided into four phases: Planning, Risk
Analysis, Engineering, and Evaluation. The software project passes through these phases in
repeated cycles, known as "spirals."

Advantages of the Spiral Model:


1. High Risk Analysis:
• Risk analysis is detailed in each phase, which helps avoid potential risks early on.
2. Ideal for Large and Critical Projects:
• This model is well-suited for large and mission-critical projects where thorough risk
management is essential.
3. Strong Documentation Control:
• There is a strong emphasis on documentation, which aids in maintaining project
quality and tracking changes.
4. Flexible for Additional Functionality:
• New features can be added in later stages as the project evolves.
5. Early Software Production:
• A working version of the software can be produced earlier in the project lifecycle.

Disadvantages of the Spiral Model:


1. Costly to Implement:
• The model can be expensive due to its iterative nature and detailed risk analysis.
2. Requires High Expertise in Risk Analysis:
• Skilled experts are needed for effective risk analysis, making it challenging for
smaller teams.
3. Project Success Depends on Risk Analysis:
• The success of the project is highly dependent on how well risks are analyzed and
managed.
4. Not Suitable for Small Projects:
• Due to its complexity, this model is less effective for smaller projects.

Q) Explain different approaches used for fast delivery of a project.


There are several approaches used for fast delivery of a project. Below are the most common ones:
1. Agile Methodology:
• Scrum and Kanban are Agile approaches that focus on iterative and incremental
development. The project is divided into small tasks (called user stories), which are
worked on in short sprints. This allows for continuous feedback and quick delivery
of working software.
2. Lean Software Development:
• Lean focuses on reducing waste and maximizing value. It eliminates non-value-
adding activities, streamlines processes, and encourages collaboration. Techniques
like value stream mapping and continuous improvement are used to speed up project
delivery.
3. Rapid Application Development (RAD):
• RAD emphasizes rapid prototyping and close customer involvement. In this
approach, prototypes are built quickly to gather requirements and validate design
choices early. This reduces time spent on planning and documentation, speeding up
delivery.
4. Extreme Programming (XP):
• XP is an efficient, flexible, and low-risk approach that helps teams manage vague or
changing requirements. It is part of Agile development, focusing on values and
principles that guide team behavior. The team is expected to be self-organized and
work closely together.

Common questions

Powered by AI

Scrum ceremonies ensure efficient project progression by structuring team interactions and improving processes. Sprint Planning aligns the team on upcoming sprint goals, Daily Scrum promotes synchronization and transparency, Sprint Review gathers feedback from stakeholders to ensure alignment with business needs, and Sprint Retrospective allows for reflection and process improvement. These structured ceremonies maintain focus, enhance communication, and foster continuous improvement .

Implementing the Spiral Model in smaller projects is challenging due to its complexity, high cost, and necessity for detailed risk analysis, requiring skilled expertise. These factors make it less efficient for small projects where simpler models suffices. Conversely, in large, critical projects, the Spiral Model's strong risk management and documentation provide necessary structure and control to manage complexities and risks effectively .

The eight core principles of Atern/DSDM are: 1) Focus on Business Need, ensuring every decision is valuable and aligned with business priorities. 2) Deliver on Time through time-boxing, providing timely outputs. 3) Collaborate to foster a one-team culture and shared understanding. 4) Never Compromise Quality by setting quality standards and regular testing. 5) Develop Iteratively to incorporate feedback and improve the project. 6) Build Incrementally from Firm Foundations for flexibility and adaptability. 7) Communicate Continuously with stakeholders for clarity and alignment. 8) Demonstrate Control through clear plans and progress reports for transparency and accountability .

The collaborative culture in Atern/DSDM positively affects team dynamics by fostering a shared ownership and mutual understanding among stakeholders, developers, and users. This inclusivity ensures diverse perspectives are integrated, enhancing decision-making quality. It encourages active participation and engagement, paving the way for shared commitment to project goals and efficient problem-solving. Collaboratively built solutions are typically more innovative and aligned to actual user needs, improving project outcomes .

Scrum's roles (Product Owner, Scrum Master, and Development Team) and ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) ensure transparency and accountability by establishing clear responsibilities and regular communication channels. Daily meetings foster synchronization and quick issue resolution, while reviews and retrospectives emphasize openness in performance assessment and process transparency. This creates a culture of accountability for delivering commitments .

Advantages of the Spiral Model include detailed risk analysis at each phase, making it suitable for large, mission-critical projects; continuous documentation for quality control; flexibility to incorporate new features; and early availability of a working software version. Disadvantages include high cost and demand for skilled risk analysis experts, leading to complexity unsuitable for small projects. The project's success heavily relies on effective risk management .

"Building Incrementally from Firm Foundations" enhances flexibility and adaptability by allowing projects to develop in manageable phases, each built on solid groundwork. This approach supports future expansion and adjustment as new insights and requirements emerge. It ensures stability in initial stages while providing the opportunity to incorporate feedback and changes iteratively, aligning with evolving business needs .

Continuous testing in both Atern/DSDM and Scrum ensures that quality standards are consistently met throughout the project, enabling early detection of issues and alignment with business requirements. It allows regular feedback, facilitates iterative improvements, and ensures that delivered products meet expectations. This practice minimizes risks associated with undetected defects and reduces the cost and time of corrective actions in later stages .

The five major components of Albrecht Function Point Analysis are: 1) External Input (EI) for input transactions updating internal files, 2) External Output (EO) for transactions extracting and displaying data, 3) External Inquiry (EQ) for user-initiated transactions that provide information without updating files, 4) Logical Interface File (LIF) as a data store accessed by the system, 5) External Interface File (EIF), a data store maintained externally but accessed by the system. Each component helps to quantitatively assess a system's functionality, aiding in estimation and project planning .

Agile methodologies such as Scrum and Kanban prioritize iterative, incremental development and continuous feedback, aligning teams on small, manageable tasks (user stories) that allow for rapid adaptation and delivery. Scrum uses fixed sprints, while Kanban emphasizes continuous workflow. In contrast, Lean focuses on waste reduction and maximizing value, using techniques like value stream mapping, while Rapid Application Development (RAD) speeds up delivery through rapid prototyping and customer involvement. Each approach suits different project needs and organizational contexts .

You might also like