Iv-Ii It Mse
Topics covered
Iv-Ii It Mse
Topics covered
[Link] Outcome
S. No. Course Outcomes (CO)
After completing this course the student must demonstrate the knowledge and ability to:
CO1 Examine the Extreme Programming basics and Agile Software Development.
CO2 Demonstrate the collaborating methods of Agile Software Development.
CO3 Demonstrate the Bug Free Development of the Software and Release.
CO4 Illustrate the mechanisms of Planning and Coding the Agile Software’s.
CO5 Develop the software with the customer requirements.
Proficiency
Program Specific Outcomes (PSO) Level assessed
by
Foundation of mathematical concepts: To use
Assignments,
mathematical methodologies to crack problem using
PSO1 3 Tutorials,
suitable mathematical analysis, data structure and suitable
Mock Tests
Algorithm.
Foundation of Computer System: The ability to
interpret the fundamental concepts and methodology of
Assignments,
PSO2 Computer systems. Students can understand the 2
Tutorials
functionality of hardware and software aspects of
Computer systems.
Foundations of Software development: The ability to
grasp the software development lifecycle and
Methodologies of software systems. Possess competent Assignments,
PSO3 Skills and knowledge of software design process. 3 Tutorials,
Familiarity and practical proficiency with a broad area of Mock Tests
programming concepts and provide new ideas and
Innovations towards research.
1: Slight
2: Moderate (Medium)
(Low) 3: Substantial (High) - : None
Course Contents
JNTU Syllabus
UNIT - I
Introduction Extreme Programming (XP) - Agile Development
Why Agile - Understanding Success, Beyond Deadlines, Importance of Organizational
Success, Introduction to Agility, How to Be Agile - Agile methods, Don't make your own
method, Road to mastery, Understanding XP (Extreme Programming) - XP life cycle, XP
team, XP Concepts, Adopting XP - Knowing whether XP is suitable, Implementing XP,
assessing Agility, Practicing XP - Thinking - Pair Programming, Energized work,
Informative Workspace, Root cause Analysis, Retrospectives
UNIT - II
Collaborating: Trust, Sit together, Real customer involvement, Ubiquitous language,
meetings, coding standards, Iteration demo, Reporting
UNIT - III
Releasing: Bugfree Release, Version Control, fast build, continuous integration, Collective
ownership, Documentation
UNIT - IV
Planing: Version, Release Plan, Risk Management, Iteration Planning, Slack, Stories,
Estimating
UNIT – V
Developing: Incremental requirements, Customer tests, Test driven development,
Refactoring, Incremental design and architecture, spike solutions, Performance optimization,
Exploratory testing
TEXTBOOK
1. The art of Agile Development, James Shore and Shane Warden, 11th Indian Reprint,
COURSE PLAN:
Link for
Reference
Course Teachin
Unit No.
Lecture
Small
Topics to be learning g
No.
Program Specific
Program Outcomes (PO) Outcomes
(PSO)
PSO1
PSO2
PSO3
PO10
PO11
PO12
PO1
PO2
PO3
PO4
PO5
PO6
PO7
PO8
PO9
CO1 3 2 2 3 2 2 1 - 1 - - 2 2 2 2
CO2 3 2 2 2 2 2 2 - 2 - - 1 1 2 2
CO3 3 3 3 3 2 2 1 - 2 - - 2 2 2 2
CO4 2 2 3 2 3 3 2 - 1 - - 2 1 2 2
DESCRIPTIVE QUESTIONS:
UNIT-I
Short Answer Questions-
[Link] QUESTION BLOOMS Taxonomy
1. Define: Successful, Challenged, Impaired L1: REMEMBER
2. Define : Method and Agile Method, Refactoring L1: REMEMBER
3. What is Iteration Planning? L1: REMEMBER
4. What is the Role of Onsite Customers? L1: REMEMBER
5. What is the role of Product Manager? L1: REMEMBER
6. What is Time Boxing, Iteration, and Velocity? L1: REMEMBER
7. How to energies the work in Agile L1: REMEMBER
8. Define Informative Workspace L1: REMEMBER
9. What is Root – Cause Analysis? L1: REMEMBER
10. Define Retrospectives L1: REMEMBER
Long Answer Questions-
[Link] QUESTION BLOOMS Taxonomy
1. Explain in detail about Organization, Technical, Personal L2:UNDERSTAND
Success
2. Explain the Principles of Agile Development L2:UNDERSTAND
3. Distinguish Traditional S/w Life cycle and Agile Life Cyle L4:ANALYZING
4. Explain the pre-requisite of adopting the XP[Extreme
L2:UNDERSTAND
Programming]
5. Explain the Assessment of Agility L2:UNDERSTAND
6. Explain the Tips for pairing L2:UNDERSTAND
7. Explain the process improvement chart with examples L2:UNDERSTAND
8. Explain in detail about root-cause analysis L2:UNDERSTAND
UNIT-2
Short Answer Questions
[Link] QUESTION BLOOMS Taxonomy
1. What are the 8 peaches that help a team and its stakeholder
collaborate? L1: REMEMBER
2. What do you mean by collaborating? L1: REMEMBER
3. What is the group dynamics involved when people work L1: REMEMBER
through team?
4. What are stand up meeting? L1: REMEMBER
5. What do you mean by coding standards? L1: REMEMBER
Long Answer Questions-
[Link] QUESTION BLOOMS Taxonomy
1. Explain the steps involved in collaborating L2:UNDERSTAND
2. Elaborate the strategies for generating trust L6: CREATE
3. Discuss in detail about the organizational strategies for
L6: CREATE
maintain impressions.
4. Criticize the daily stand up meeting L5:Evaluate
5. Demonstrate the Iteration Demo Process L2:UNDERSTAND
UNIT-4
Short Answer Questions-
[Link] QUESTION BLOOMS Taxonomy
1. What is product vision and how to identify the vision? L1: REMEMBER
2. Distinguish release early and release often L6: CREATE
3. What do you mean my adaptive planning? L1: REMEMBER
4. Define Risk Management L1: REMEMBER
5. Assess the iteration planning L5:EVALUATE
Long Answer Questions-
[Link] QUESTION BLOOMS Taxonomy
1. Discuss the vision statement & promote it to stakeholder L6: CREATE
2. Explain the method to create a release plan L2:UNDERSTAND
3. Design the strategy for Game and Play to win L6: CREATE
4. Discuss how can we make a release commitment? L6: CREATE
5. Explain in detail about estimation and velocity L2:UNDERSTAND
UNIT-5
Short Answer Questions-
[Link] QUESTION BLOOMS Taxonomy
1. Define Customer Review Questions L1: REMEMBER
2. What do you mean by Multiple name / Value pair? L1: REMEMBER
3. What is unit test? L1: REMEMBER
4. Define refactoring L1: REMEMBER
5. What do you mean by Risk – Driven Architecture L1: REMEMBER
UNIT -2
UNIT -3
1. Select the option that suits the Manifesto for Agile Software Development
a) Individuals and interactions
b) Working software
c) Customer collaboration
d) All of the mentioned
2. Agile Software Development is based on
a) Incremental Development
b) Iterative Development
c) Linear Development
d) Both Incremental and Iterative Development
3. How many phases are there in Scrum ?
a) Two
b) Three
c) Four
d) Scrum is an agile method which means it does not have phases
4. How is plan driven development different from agile development ?
a) Outputs are decided through a process of negotiation during the software development
process
b) Specification, design, implementation and testing are interleaved
c) Iteration occurs within activities
d) All of the mentioned
5. Which of the following does not apply to agility to a software process?
a) Uses incremental product delivery strategy
b) Only essential work products are produced
c) Eliminate the use of project planning and testing
d) All of the mentioned
UNIT 4
1. ------------------- is not a conflict in software development team?
a) Simultaneous updates
b) Shared and common code
c) Versions
d) Graphics issues
2. Which of the following is not a typical environment in communication facilitation?
a) Multiple teams
b) Multiple user groups
c) Multiple fests
d) Multiple locations
3. Which of the following is not a part of Software Configuration Management Basics?
a) Identification
b) Version
c) Auditing and Reviewing
d) Status Accounting
4. What is one or more software configuration items that have been formally reviewed and
agreed upon and serve as a basis for further development?
a) Configuration
b) Baseline
c) Software
d) All of the mentioned
5. Why is software difficult to build ?
a) Controlled changes
b) Lack of reusability
c) Lack of monitoring
d) All of the mentioned
Fill in the blanks:
1) ------------------ is a specific instance of a baseline or configuration item?
2. ITG stands for-----------------------------
3 Which one is not a software quality model?
a) ISO 9000
b) McCall model
c) Boehm model
d) ISO 9126
4. IMC Networks is a leading ________ certified manufacturer of optical networking and
LAN/WAN connectivity solutions for enterprise, telecommunications and service
provider applications.
5. Software reliability is defined with respect to----------------------
UNIT 5
1. The team is unable to decide whether it makes sense to buy an off-the-shelf from the
vendor or go about building it themselves. Both options have its merits and demerits. As a
Scrum Master what would be your recommendation to the team? --------------------------
CSE IV YEAR II SEM Page 16
a). Consult with the product owner of what he is willing to sponsor.
b) Conduct a spike to evaluate both options.
c)Do a fist of five voting.
d) None of the above.
2. ________ is a low-fidelity prototype that shows a mockup for a set of screen, containing
the basic layout of the different widgets on it
a)Persona
b)Wireframe
c)Spikes
d)Story map
3. If you happen to hire for a new Agile team, you should prefer:
a) Developers
b) Specialists in the technologies to be used
c)Generalists with cross-functional skillsets
d) People who exhibit adaptive leadership skill
4. During which Scrum ceremony are risk audits held?
a) Sprint planning b)Sprint execution c)Sprint review d)Sprint retrospective
5. By tracking velocity trends, a team can---------
a). Gauge the rate of progress b)Estimate how much longer it will take to complete
c)Correcting estimation errors d) All of the above.
Fill in the blanks :
[Link] pillars of Scrum are-----------and-----------------------
2. XP teams use the technique of ________ to enhance code quality, while keeping its
behavior unchanged.
3. During which Scrum ceremony are risk audits held?-----------------------------
4. The Y-axis of an iteration burndown chart depicts ----------------------
5. The pillars of Scrum are----------------------------
Answers
1. Transparency, Inspection [Link] [Link] execution [Link] of features to be compleraed
5. Transparency, Inspection and Adaptation
GATE QUESTIONS
Not Related
WEBSITES
1. [Link]
2. [Link]
3. [Link]
JOURNALS
1. [Link]
[Link]
2. [Link]
3. [Link]