Tags: %TAGME{ tpaction="" web="Main" tag="" }% view all tags

Discussion Questions

Agile Software Development

  1. Are certain countries more/less likely to adopt agile methods?

  2. How precisely should requirements be defined if agile methods are used?

  3. At what point is the software model no longer agile or waterfall, but rather a hybrid of the two? Is there a name for that besides methods like Scrum?

  4. I don’t quite understand how one could write the tests for the code before the code is written. Does this mean write the physical test code, or conceptually think about the tests that one would write for the software?

  5. How do you integrate requirements elicitation in the development stage? How do companies benefit from doing this?

  6. What are some differences between plan-based development and requirements engineering? Is one better suited for certain scenarios?

  7. I know that pair-programming exercises are used at a lot of companies as part of a technical interview. What sorts of things might an interviewer be looking for in a pair-programming interview - more errors caught, refactoring, commenting on code chunks?

  8. When thinking about collective ownership, the issue inevitably comes up where someone might not be pulling their weight or consistently causes issues, such as the same bugs. How do we deal with this, especially in a setting where everyone is supposed to be accountable?
  9. What are some examples when extreme programming is completely ineffective?

  10. The text claims that tool support is used to support the agile development process. Tools such as automated testing tools and tools to support configuration management. What are these tools and how exactly do they function?

  11. What are the factors that affect the choice of plan-based or agile development?

  12. In practice, a mix of agile and plan-based techniques may be used to develop a system. What are the special systems that can be developed by only using one technique?

  13. How do you know if it is better to use a pre-made model or make your own model when engineering software.

  14. How realistic is it for the tester to be able to stay on par with the development of the system in test-first development?

  15. This chapter focuses on testing as a way to decrease development time as you can find errors earlier which will save time in the future. I wanted to point out that “collaborative development practices have been shown to find a higher percentage of errors than testing does, and they cost less than half as much per error found as testing does” (McConnell, 2004). Cost, in this case, is equivalent to time since you are paying programmers for their time to find errors.

  16. Are agile methods able to produce quality software with a reasonable amount of consistency?

  17. Can you speak more about automated testing? What are some popular frameworks? What goes into coding a test?

  18. The books lists that some tests being difficult to write incrementally is a problem in ensuring test coverage. Can you elaborate on what this means and give a few examples?

  19. The book mentioned several times that agile methods do not work the best with maintenance. How then do companies and teams plan ahead for maintenance and evolution?

  20. What do disciplined agile delivery and agility at scale look like in practice? What are some examples of products/companies that would utilize that?

  21. The book mentioned that Agile is particularly useful in larger projects as it decreases the planning cost, but later it also mentioned Agile presents several realistic problems when dealing with larger projects?

  22. Is the traditional project management still the better option for smaller project?

  23. How effective is designated leadership in a team engineering software?

  24. How does a team of developers decide on what methods to use when there are disagreements to which one is a better fit?

Topic revision: r1 - 2020-01-23 - JimSkon
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback