2- Marks

S.No. COs Questions K W

1 CO1 What are different types of Agile based Methodologies or frameworks that K1 E
available to develop a Software

• Scrum

• Extreme Programming

• Feature Driven Development

• Lean Software Development

• Crystal

• Kanban

2 CO1 Interpret the advantages and Disadvantages involved in Agile Process K2 M

Pros:

• In Agile methodology the delivery of software is unremitting.

• The customers are satisfied because after every Sprint working feature
of the software is delivered to them.

• Customers can have a look of the working feature which fulfilled their
expectations.

• If the customers has any feedback or any change in the feature then it
can be accommodated in the current release of the product.

Cons:

• In Agile methodology the documentation is less.

• Sometimes in Agile methodology the requirement is not very clear

hence it’s difficult to predict the expected result.

• In few of the projects at the starting of the software development life

cycle it’s difficult to estimate the actual effort required.

3 CO1 Predict the disadvantages of RAD Model. K2 E

The central theme of RAD is based on designing quick and dirty prototypes,
which are then refined into production quality code
 The developers using the RAD model focus on developing all the features of an
application by first doing it badly and then successively improving the code
over time.

4 CO1 State the merits and demerits of incremental model K2 E

• The development process based on the Incremental model is split

into several iterations (“Lego-style” modular software design is
required!).

• New software modules are added in each iteration with no or little

change in earlier added modules.

• The development process can go either sequentially or in parallel.

Cons:

The requirements of the software are divided into several modules that can be
incrementally developed and delivered. The core features are developed first
and the whole software is developed by adding new features in successive
versions.

5 CO1 Define Spiral Model and Describe its disadvantages K1 M

• The Spiral model puts focus on thorough risk assessment.

• Thus, to reap the benefits of the model to the fullest, you’ll need to
engage people with a strong background in risk evaluation.

• A typical Spiral iteration lasts around 6 months and starts with 4

important activities - thorough planning, risk analysis, prototypes
creation, and evaluation of the previously delivered part.

• Repeated spiral cycles seriously extend project timeframes.

• This is the model where intensive customer involvement appears. They

can be involved in the exploration and review stages of each cycle.

• At the development stage, the customer’s amendments are not

acceptable.

6 CO1 Give short note on the process of Verification and Validation involved in K1 E
Software Development.

Verification testing includes different activities such as business requirements,

system requirements, design review, and code walkthrough while developing
a product.
 It is also known as static testing, where we are ensuring that "we are
developing the right product or not". And it also checks that the developed
application fulfilling all the requirements given by the client.

Validation testing is testing where tester performed functional and

non-functional testing. Here functional testing includes Unit
Testing (UT), Integration Testing (IT) and System Testing (ST),
and non-functional testing includes User acceptance testing (UAT).

7 CO1 Define Agile Methodology K1 E

• Agile breaks down larger projects into small, manageable chunks

called iterations

• The product produced during each iteration should be able to be put

into the world to gain feedback from users or stakeholders

8 CO1 Specify the significance of Iterations K1 E

This means customers can get an insight into the product before it is fully
finished and add their feedback to improve the development process. In Agile
iterations, steps are repeated on a loop until an optimal end result is achieved.

9 CO1 What are different phases involved in designing throughout the life cycle in K1 E
agile Methodology?

10 CO1 Define Test Driven Development (TDD) K1 E

• TDD= Refactoring + TFD (Test First Development)

• Add a test.

• Run all tests and see if any new test fails.

• Write some code.

• Run tests and Refactor code.

 • Repeat.

11 CO1 Define Agility K2 E

Agility is the state of being (not just doing) Agile, which means going beyond
its “well-known” practices. It requires you to understand that there's always
room for improvement to tailor your products/services

12 CO1 Mention the tools that can be useful for screenshots while working on agile K1 M
projects

ATLASSIAN JIRA

AGILO for Scrum

13 CO1 Mention about the genesis of Agile Methodology K1 M

• Agile software development refers to software development

methodologies centered round the idea of iterative development,
where requirements and solutions evolve through collaboration
between self-organizing cross-functional teams.

• The ultimate value in Agile development is that it enables teams to

deliver value faster, with greater quality and predictability, and greater
aptitude to respond to change.

• Scrum and Kanban are two of the most widely used Agile
methodologies

14 CO1 List any two metrics of the Lean Software Development K1 E

• Eliminate Waste

• Build Quality In

• Create Knowledge

• Defer Commitment

• Deliver as fast as possible

• Respect People

• Optimize the Whole

15 CO1 Write down the Agile Principles? K1 E

1) Highest priority is to satisfy the customer

 2) Welcome changing requirements, even late in development

3) Deliver working software frequently

4) Effective method of conveying information to and within a

development team

5) Business people and developers must work together

6) Build projects around motivated individuals and the best way is face to
face conversation.

7) Working software is the primary measure of progress

8) Promote sustainable development

9) Continuous attention to technical excellence and good design enhances

agility

10)Simplicity

11)The best architectures, requirements, and designs

12)At regular intervals, the team reflects on how to become more

effective, then tunes and adjusts its behavior accordingly

16 CO1 Differentiate between iteration plan and release plan K2 M

17 CO1 State the intricacies available in wrongly prioritizing the backlog K2 M

► Working on low priority feature which is not important for minimal

viable product is waste Any Rework is the complete waste.
 ► Using library which is does not the fulfill current requirement.

► In Middle of the work if you have to change it will require lots of efforts.
This is the complete waste of development testing and team efforts.

18 CO1 Label and describe the phases involved in Agile design practices K1 E

19 CO1 Illustrate the concept of Acceptance Test Driven Development (TDD) K1 M

Acceptance test–driven development (ATDD) is a collaborative process where

developers, testers and business representatives come together to work out
requirements, perceive potential pitfalls and reduce the chance of errors
before coding begins

20 CO1 Write down the two levels of TDD K1 E

1. Acceptance TDD (ATDD) or Behavior Driven Development (BDD)

-With ATDD you write a single acceptance test, or behavioral
specification depending on your preferred terminology, and then just
enough production functionality/code to fulfill that test. The goal is to
specify detailed, executable requirements for your solution on a just in
time (JIT) basis.

2. Developer TDD- write a single developer test, sometimes inaccurately

referred to as a unit test, and then just enough production code to fulfill
that test. The goal is to specify a detailed, executable design for your
solution on a JIT basis.

21 CO1 State Continuous Integration K1 E

 ► XP teams keep the system fully integrated at all times.

► We say that daily builds are for wimps: XP teams build multiple times
per day.

► Infrequent integration leads to serious problems on a software project

as,

► although integration is critical to shipping good working code,

the team is not practiced at it

► infrequently integrated code is often a buggy code.

► weak integration process leads to long code freezes.

22 CO1 Name the benefits of TDD K1 E

Benefits

Makes finding mistakes easy.

You express your intent twice, once with a test and another with production
code.

All these tests are checked in and become part of your continuous integration.

23 CO1 Classify the Similarities and Differences between Continuous Integration and K2 D
Continuous Deployment

24 CO1 Predict the flow of Refactoring Process available in Agile Methodology K1 M

 • “A change made to the internal structure of software to make it easier
to understand and cheaper to modify without changing its observable
behavior”

25 CO1 Define Pair Programming and list out the benefits K1 E

• Continuous code review

• Have less defects

• Better code & solutions

• Knowledge Sharing

• Efficiently welcome new members

26 CO1 Phases of Disciplined Agile Delivery Life Cycle K2 M

27 CO1 Mention four Key Principles of Refactoring K1 M

• Coding standards

• Pair programming

• Simple design

• Tests

• Continuous integration

28 CO1 Write in short about user story K3 M

• user stories are small, much smaller than other usage requirement
artifacts such as use cases or usage scenarios, which is written by
customers and not developers.

29 CO1 Define Themes K2 E

 • A theme is a collection of related user stories.

• For example, for a university registration system there might be

themes around students, course management, transcript generation,
grade administration, financial processing.

30 CO1 What is Epic and its significance K2 E

An agile epic is a body of work that can be broken down into specific tasks
(called user stories) based on the needs/requests of customers or end-users.

31 CO2 Elucidate all the practices involved in Lean Software Development K1 E

Methodology

• Eliminate Waste

• Build Quality In

• Create Knowledge

• Defer Commitment

• Deliver as fast as possible

• Respect People

• Optimize the Whole

32 CO2 Write down various levels of planning techniques indulged in Agile K2 E

Methodology

33 CO2 Define Scrum K1 E

 ► SCRUM is an agile, lightweight process for managing and controlling
software and product development in rapidly changing environments.

´Iterative, incremental process

´Team-based approach

´developing systems/ products with rapidly changing requirements

´Improve communication and maximize cooperation

´Protecting the team from disruptions

´A way to maximize productivity

34 CO2 Label three pillars of Empricism K1 M

Three Pillars of Empiricism in Scrum | Transparency, Inspection, Adaptation.

35 CO2 Define Empricism K1 E

Empiricism in Scrum is an approach whereby the team continuously learns

and improves from mistakes. In Scrum, empiricism means that the team
makes decisions and changes based on what the customer is actually
experiencing, rather than what the developers intended them to experience.

36 CO2 List out those values involved while scrum is adapted in developing a software K1 E
A team's success with scrum depends on five values: commitment, courage,
focus, openness, and respect.

37 CO2 Describe why openness is required for successful implementation of scrum K1 M

► The Scrum induction requires transparency and openness.

► We need to investigate reality with a specific end goal to make sensible

adjustments.

► Team members should be open about their work, progress, what they
learned and the issues they are facing

38 CO2 Short note on various kinds of Commitment involved while adapting Scrum K1 M
framework

► Scrum teams must be committed to progress and willing to have

practical objectives and stick to them. This is a team activity where you
 are a part of a team, and you are accountable to work together and to
conform to your commitments.

⮚ Sprint-based commitment

⮚ Commitment as a team

⮚ Commitment as an individual

39 CO2 Short script on different project phases of scrum K1 M

🠶 The Pregame Phase

► ´Planning

► ´System Architecture/high Level Design

🠶 The Game Phase

🠶 The Post Game Phase

40 CO2 State all the rules to be followed while you are planning to incorporate agility K1 M

1. Initiation. The agile transformation begins when leaders are aligned on

their vision for the process. ...

2. Training. ...

3. Piloting. ...

4. Retrospection. ...

5. Launch. ...

6. Sustain.

41 CO2 Develop a product backlog for ticket vending system K3 D

Let us look at a small list of items that could be part of a Product Backlog. Each
item in the backlog is essentially a short description of a requirement to meet
the need of the customer or add value to customer.
Let us consider a ticket booking system project
 Description

1 Utility to display all Unpaid tickets

2 Utility to display all Cancellations

3 Fix bug in display of Paid Tickets

4 Implement indexing in the database to improve data retrieval time

5 Write User Manual for ticket booking system

42 CO2 Write a user story for the requirement “The System should have options for K3 D
Creating, Modifying and Deleting a Book detail”

How do you write a user story for system requirements?

Tips for working with user stories

1. Don't write too many details and don't write the stories too early. Write
them when they are needed and sick to the template. ...

2. It is better to write small user stories than large. ...

3. Define what the minimum amount of critical requirements is. ...

4. Improve functionality incrementally.

43 CO2 State the role of Scrum Master in the Agile Project Phase K1 M

🠶 Represents management to the project

🠶 Responsible for enacting Scrum values and practices

 🠶 Removes impediments

🠶 Ensure that the team is fully functional and productive

🠶 Enable close cooperation across all roles and functions

🠶 Shield the team from external interferences

44 CO2 List out the Process of Sprint Backlog K2 E

A sprint backlog is a list of work items your team plans to complete during a
project sprint. These items are usually pulled from the product backlog during
the sprint planning session. A clear sprint backlog prevents scope creep by
clarifying exactly what your team will be doing—and not doing—during each
sprint.

45 CO2 What is the difference between burn-up and burn-down charts? K2 M

A display of what work has been completed

and what is left to complete

´one for each developer or work item

´updated every day

´(make best guess about hours/points

completed each day)

´ variation: Release burn down chart

´shows overall progress

´updated at end of each sprint

46 CO2 Write about Sprint Planning meeting and give pictorial representation for K.
planning a new sprint.
47 CO2 Distinguish Sprint Backlog and Product Backlog K2 M

48 CO2 Describe about four different steps involved in game phase of software that is K2 D
rigorously adapting Scrum framework

► Develop(analysis , design, develop)-the team analyze current situation

of the product , think what changes have to be made for
implementation of backlogs requirements into the packets , design the
process and finally proceed to development , implementation , testing
and documenting the changes.

► Wrap-closing packets

► Review-meetings for presenting current work and progress , resolving

problems , adding new backlog items , risk review.
 ► Adjust-the information gathered during the review is consolidated into
affected packets.

49 CO2 What are the different ways to estimate the total amount of time and work to K3 M
be invested in completing the product as per the user story given by the
customer

► Considered a team has 6 members,

► committed to work full time of 8 hours a day on a project

► no member is on leave during iteration,

then the task capacity for two-week iteration will be,

6(members) x 8(hours) x 10(days) = 480 hours

50 CO2 Identify the characteristics of Crystal methodology K1 E

• Human-powered. This simply emphasizes that people are the most

vital element of Crystal, and all the processes and tools are relative to
them. It also means that people are capable of organizing themselves.
As the processes develop, they can become more organized and
competent.

• Adaptive. An approach and not a set of prescribed tools and

techniques for software development, Crystal is a stretch to
methodology. This means that processes and tools are not fixed, but
rather adjusted in order to meet the requirements of the team and the
project at hand.

• Ultra-light. Not advocating too much documentations, management,

and reporting, Crystal is known as a “lightweight methodology.” It
focuses on practicing open communication between team member and
transparent workflow between the team and the client.

51 CO2 Define Feature Driven Development (FDD) K1 E

FDD is an agile, highly adaptive software development process that is

• Highly and short iterative.

• Emphasizes quality at all steps

• Delivers frequent, tangible working results at all steps

 • Provides accurate and meaningful progress and status
information, with the minimum of overhead and disruption for
the developers.

• Is liked by client, managers and developers

52 CO2 List out all those Key roles involved in completing a product by adapting FDD K2 E
and also write a short note on each

• Speculate: Speculate replaces the deterministic word planning,

planning of product specifications or planning of project management
tasks.

• Collaborate:

1. Collaborate represents drawing a balance between Managing in the

traditional project management sense, and Creating and maintaining
the collaborative environment needed for emergence.

2. Collaborative Activities build products, keeping up the pace of changes

in the environment.

• Learn: Learn aims both, the developers and the customers, to use the
results of each development cycle to learn the direction of the next.

53 CO2 Sketch out the Adaptive Software Development (ASD) Life cycle K3 E

54 CO2 What are the couple of keyways to be adapted in achieving full-fledged K2 M

Adaptive Development

• The Adaptive model is built from a different point of view.

• Though cyclical like the Evolutionary model, the names of the phase
reflect the unpredictable nature of increasingly complex systems
 ► Adaptive Development goes further than its evolutionary heritage in
two key ways-

1. It explicitly replaces Determinism with Emergence.

2. It goes beyond a change in life cycle to a deeper change in management

style.

55 CO2 Define Crystal methodology K1 E

The Crystal method is among the more flexible agile frameworks, because it is
designed around a project’s people and is not dependent on any single set of
processes or tools. In that sense, it can be a viable methodology for
organizations that want to empower their teams to work however they deem
most effective.

56 CO2 List out the properties of Crystal Methodology K1 E

► Frequent Delivery

► Reflective improvement

► Close or osmotic communication

► Personal safety

► Focus

► Easy access to expert users

► Technical environment with automated tests, configuration

management, and frequent integration

57 CO2 Categorize various Crystal methodologies to be adopted based on the K2 D

complexity of the product to be developed

► Crystal method is actually comprised of a family of agile methodologies

in different variants (colors), each of which has unique characteristics
driven by several factors such as team size, system criticality, and
project priorities.
 ► The following are just some of the practically used crystal
methodologies in real projects:

► Crystal Clear – for teams consisting of 6 people.

► Crystal Yellow – for teams consisting of 10-20 people.

► Crystal Orange – for teams consisting of 20-40 people.

► Crystal Red – for teams of up to 80 people.

► Crystal Maroon – for teams of up to 200 people.

► Crystal Diamond

For large projects with huge teams

where there is a potential risk to human life

► Crystal Sapphire

58 CO2 Specify the Pros and Cons of Crystal Methodology K1 M

► Crystal’s Advantages:

• Allows teams to work the way they deem most effective

• Facilitates direct team communication, transparency and

accountability

• The adaptive approach lets teams respond well to changing

requirements

► Crystal’s Disadvantages :

• Lack of pre-defined plans can lead to scope creep

• Lack of documentation can lead to confusion

59 CO2 Define Extreme Programming K1 E

• Dynamically changing software requirements

 • Risks caused by fixed time projects using new technology

• Small, co-located extended development team

• The technology you are using allows for automated unit and functional
tests

60 CO2 List out all the practices involved Extreme Programming K1 E

 16- Marks
S.No. COs Questions K W
1 CO1 Illustrate various generic software models formerly used to develop a K3 D
software. Compare those generic models with the Agile methodology in
different aspects by implementing in developing a E-ticket booking Software

2 CO1 Explain in detail about Test Driven Development (TDD) K2 E

3 CO1 Elucidate the significance of Pair Programming in detail and also do describe K2 M
what are the do’s and don’ts of pair Programming. How it can be effectively
utilized

4 CO1 Describe in detail about Continuous Integration (8) K2 M

5 CO1 Script down how the products are designed and developed in agile (8) K2 M

6 CO1 Describe about User Stories and develop a user story for trip planning K3 M
system

7 CO1 Construct the incremental delivery of an infrastructure flyover project in K3 D

agile software development concept with neat diagram

8 CO1 Apply the refactoring four key Principles for Medical and business K3 D
applications

9 CO1 Discuss about the Agile Manifesto and 12 Principles of Agile Methodology (8) K1 M

10 CO1 Draw the simple design of ATM using User Stories (8) K2 M

11 CO1 Discuss Agile Project Management and its advantages with appropriate K2 M
examples

12 CO1 Explain about Refactoring K2 M

13 CO1 Explain in detail about Test Driven Development with suitable Case Study. K2 D

14 CO1 Write about classification of Agile Methods and give a detailed note on scrum K2 E
framework
15 CO2 Illustrate in detail about Extreme Programming and pen down how an K3 D
extreme programming can be adopted in developing a banking system

16 CO2 Explain in detail about Adaptive Software Development (ASD) Methodology K2 E

(8)

17 CO2 Infer what are all the ways available in predicting the overall time estimation K2 D
in completing a product by means of adopting Scrum Framework (8)

18 CO2 Explain how Crystal methodologies can be adopted for developing products K2 M
ranging from low complexity to higher without any sort of discrepancy

19 CO2 Explain in detail about Lean Software Development Methodology K2 M

20 CO2 Elucidate in detail about Roles, Events and Artifacts of Scrum Framework. K3 M
Also incorporate Scrum for developing a Library Management System

21 CO2 Develop the Product backlog and Sprint Backlog for online shopping Website K3 D

22 CO2 Develop the Product backlog and Sprint Backlog for online ticket reservation K3 D

23 CO2 Draw an Overview diagram of Scrum roles and Discuss about the various K2 M
points of Product Backlog and Sprint Backlog.

24 CO2 Write Short note on Project Velocity and Burndown Chart. (8) K2 E

25 CO2 List any four tools which are used in Agile Project Management. (8) K3 E

26 CO2 Describe about Product backlog, scrum Team, Project budget in Scrum K3 M
Management with suitable Case Study

27 CO2 Discuss about team dynamics, team size, team composition, team K3 E
responsibility and authority in scrum teams

28 CO2 Describe in detail about Feature Driven Development (FDD) K2 M