Skip to content
- What are the individual stages of refactoring?
- How to judge the completeness of a set a of tests used in the agile methods?
- What problems might arise of having a user closely involved during
- software development? Is there a way to avoid them?
How would an XP be able to write tests for a system if the specifications are unclear or changing? - Should our projects incorporate pair programming? If so, should the decision on how to co-operate rest upon the entire team or the pair itself?
- What are the key differences between XP and Scrum?
- Why are story cards used as a means of identifying requirements? Would it not just be easier to
- state requirements outright, even if requirements are uncovered incrementally?
- If we implement agile development during our projects, will we be required to define specific
- roles for each other as in the Scrum approach?
- Why can’t teams using incremental development just create documentation after each
- increment is complete?
- There are so many downsides to agile development in large companies developing large, long-term projects. Is it even worth pushing for small moves toward agile development?
- What is the difference between scaling up and scaling out?
- What are the disadvantages of the informality of the agile method?
- What are real life examples of Scrum?
- Are there examples of big scale teams using agile methods?
- Discuss Scrum and talk about why it is used in software development?
- Is it possible to develop an entire software product using solely the agile method?
- Discuss Scrum and talk about why it is used in software development?
- Is it possible to develop an entire software product using solely the agile method?
- Why would one use agile development over plan-based development?
- What are some scenarios where agile development cannot be used?
- Is it more likely to accept XP for in-house development rather than someone developing a system for you? (Documentation might be less crucial if developed and used in-house.)
- Would you be able to divide and conquer in pair programming? The entire point is to work as a pair to catch each other’s errors but you might be able to work faster if you divide and conquer but check each other’s work after each short step.
- How is the scrum cycle different from a regular agile development process? How is it better for some situations? (I was still a bit confused about this after the reading)
- How does one design for a change during software development? What do such designs look like?
- Why might Agile not work well in a team that has a wide range of skills and abilities?
- What are the pros and cons of testing before you write the code?
- Why is it necessary to introduce some methods and documentation from
- plan-based approaches when scaling agile methods to larger projects that
- are developed by distributed development teams?
- Could you give specific examples of scenarios where each principle of agile software development would be beneficial?
- How can a designing team decide how many story cards are enough to include in their specification tests for the developing program? And how can a program in the extreme programming process account for changes/addition of specification (story cards) in its design?
- What does it mean that agile development focuses on the code rather than the design?
- What is the difference between test-first and test-driven development?
- Taking in consideration the costs, pros and cons, is extreme programming worth it?
- How realistic are the agile methods in the project we are developing in this class?
