AL-703 (C) · Agile Software Development/Unsolved PYQ Paper
AL-703-C Agile Software Development - Nov 2023 Question Paper
Under each question, How to answer lists the points an answer should cover, outlined by CampusPrep from the syllabus. Check the details against your textbook.
-
7 MarksaWith a neat sketch discuss about the primary roles of Feature driven development in agile.
How to answer
- Define Feature Driven Development (FDD) in Agile context
- List primary roles: Project Manager, Chief Architect, Development Manager, Chief Programmer, Class Owner, Domain Expert
- Explain responsibilities of each role briefly
- Provide neat sketch showing role hierarchy / interaction
-
7 MarksbWho are the key stakeholders in Agile product development? Explain their responsibilities.
How to answer
- Define Agile stakeholder concept
- Identify key stakeholders: Product Owner, Scrum Master, Development Team, Customers/Users, Sponsors/Management
- Explain responsibilities of each stakeholder
- Link responsibilities to product value delivery
-
7 MarksaDifferentiate scrum Vs Kanban.
How to answer
- Define Scrum and Kanban briefly
- Compare on basis: cadence, roles, artifacts, WIP limits, change policy
- Present differences in tabular form
- Conclude suitability of each approach
-
7 MarksbWhat are the different roles performed within an XP team? Explain.
How to answer
- Define XP team concept
- List roles: Customer, Programmer, Tester, Tracker, Coach, Manager/Doomsayer
- Explain duties of each role
- Show how roles collaborate in XP
-
7 MarksaHow do you monitor and control the agile products.
How to answer
- Define monitoring and control in Agile
- List techniques: daily standup, burn charts, velocity, Kanban board, reviews
- Explain how metrics control scope, time and quality
- Mention Product Owner and Scrum Master roles
-
7 MarksbExplain the different steps in the involved in the agile Retrospectives.
How to answer
- Define Agile Retrospective purpose
- List steps: Set the stage, Gather data, Generate insights, Decide what to do, Close
- Explain activities in each step
- Emphasize continuous improvement outcome
-
7 MarksaHow do sprints work in Agile? What are the four phases of sprint in Agile? Explain in detail each phases.
How to answer
- Define Sprint in Agile/Scrum
- Explain how sprints work: planning, execution, review, retrospective
- List and explain four phases in detail
- Mention timebox, sprint goal and increment
-
7 MarksbDiscuss about the various scrum artifacts used during the main activities.
How to answer
- Define Scrum artifact concept
- List artifacts: Product Backlog, Sprint Backlog, Increment
- Explain purpose and use in main activities
- Mention commitments: Product Goal, Sprint Goal, Definition of Done
-
7 MarksaDiscuss the principles of scrum planning in detail.
How to answer
- Define Scrum planning levels
- List principles: prioritization, estimation, timeboxing, collaboration, velocity-based planning
- Explain each principle in detail
- Link to release and sprint planning
-
7 MarksbIdentify and discuss the role played by the extreme programming team.
How to answer
- Define Extreme Programming team
- Identify roles: Customer, Developer, Tester, Tracker, Coach
- Discuss role played by team in XP practices
- Highlight collaboration and collective ownership
-
7 MarksaExplain the following:
- i)Thinking-pair programming of XP
- ii)Collaboration of XP
How to answer
- Define pair programming / thinking-pair concept in XP
- Explain driver-navigator collaboration and benefits
- Define collaboration practice in XP
- Mention quality, knowledge sharing and continuous feedback
-
7 MarksbWhat are the key phases in the Extreme Programming (XP) lifecycle and how does XP differ from traditional software development methodologies?
How to answer
- List key XP lifecycle phases: Exploration, Planning, Iterations, Production, Maintenance, Death
- Explain activities in each phase
- Compare XP vs traditional waterfall: iterative, customer involvement, change handling
- Conclude advantages of XP
-
7 MarksaWhat is the need and significance of refactoring.
How to answer
- Define refactoring
- Explain need: remove code smells, improve design and maintainability
- Discuss significance for Agile: technical debt, readability, extensibility
- Give examples of refactoring benefits
-
7 MarksbHow do you ensure that refactoring doesn't introduce new bugs or regression in an Agile project?
How to answer
- Define regression risk in refactoring
- List safeguards: automated tests, TDD, continuous integration, code reviews
- Explain small incremental refactoring and Definition of Done
- Mention burn-down/velocity unaffected by safe refactoring
-
14 MarksWrite short notes on any two of the following:
- a)Continuous Integration of Agile
- b)Burn down chart
- c)Agile manifesto
- d)Technical Debt
How to answer
- Select any two topics from the four options
- Define each chosen concept clearly
- Explain key practices, purpose and benefits
- Give example / diagram where relevant
Go to where you left off?
Quick Add to Notes
Save questions, your own notes and screenshots into notes filed by unit. It takes a free account.
Create free accountHave an account? Log in
Notes Panel