i have to give a presentation on agile methodology. i have prepared advantages and disadvantages.. but im stuck in situations in which this particular method is suitable to apply. can any one out there help me? plz

Dani AI

Generated

Following 's suggestion to compare methodologies, this short, practical note gives a crisp decision checklist for when Agile is a good fit and supplies ten focused interview questions for 's visit.

When Agile is a good fit:

  • Requirements are unclear or likely to change; iterative work lets priorities evolve (Agile Manifesto).
  • Fast feedback from users or the market is available and valuable.
  • Teams are small-to-medium, cross-functional, and can meet regularly (day-to-day collaboration) (Scrum Guide).
  • The product can be delivered in incremental value slices (features, not a single big deliverable).
  • Continuous integration/automation is possible and releases can be frequent.
    For large programs or heavy-regulation projects consider scaled or hybrid approaches rather than pure Agile (Atlassian Agile vs Waterfall).

When Agile is less suitable:

  • Contractually fixed scope/fixed-price work without mechanisms for change control.
  • Regulatory processes demanding waterfall-style gated approvals, unless compliance activities are explicitly integrated into sprints.
  • Work that cannot be decomposed into vertical slices (massive legacy rewrites) without an initial architectural refactor.

Ten precise interview questions (short rationale in parentheses):

  1. Which Agile frameworks do you use (Scrum, Kanban, XP) and why? (choice rationale)
  2. Typical iteration length and how it was chosen? (cadence)
  3. How are requirements captured and prioritized into the backlog? (governance)
  4. How often do you release to users and what CI/CD tools do you use? (delivery)
  5. How is testing/QC integrated into each iteration? (quality)
  6. How are non-functional and compliance requirements tracked? (traceability)
  7. How is estimation done and how are scope changes handled in fixed‑price work? (contracts)
  8. Which metrics track progress and health (velocity, cycle time, defects)? (measurement)
  9. How do remote or distributed members collaborate day-to-day? (coordination)
  10. Can you show recent artifacts (backlog, burndown, release plan) or a concrete example where Agile changed an outcome? (evidence)

For background reading and concise definitions refer to the Agile Manifesto and the Scrum Guide linked above.

Recommended Answers

All 5 Replies

It may be helpful to compare/contrast it with another software development methodology. Agile Methodology is centered around organizing teams from veritable backgrounds together to complete a project. Other methodologies may be focused on ... [fill in the blank]

You said you already have the pros and cons laid out, so you just need some situations where you can decide what method you would use. You may also use several methodologies within the same project.

As small team of Java coders may be using one method to organize themselves, while another team may use a methodology that fits their paradigm. A business team may be sponsoring the project, for example, but they might use another methodology. When the two (and other teams) come together, they may govern their interaction with yet another methodology!!

I hope this helps.

Good Luck

presentation was great..... now im asked to visit any software house and take an interview from a member about what methodologies they use and why......
ive to submit a questioner to my teacher which states that what im going to ask him in the interview. could any one related to this field, suggest me the questions that i should ask? actually im not a software student. im a programmer.. so , my know how about this , is very less.. n this is the very 1st time, im given this course... :/
plz help.. suggest 5 to 10 questions or give me hint. ill do it by my self then.. :)

If you are a programmer, are are in the related field ... And programming IS making software!!

So you will use some methodology whether it is the "fly by the seat of your pants" method and making spaghetti code, or organizing your time, resources, abilities, and ultimately, your code using a standardized method.

Here are some basic questions (that may help you develop more):
-What Methodologies does your company use?
-What Methodologies do you find useless?
-Why . . . ?
-When . . . ?
-How . . . ?
-Where . . . ?
-Who . . . ?

It may help to focus your questions on what makes a good employee... How those that don't play by the rules (established methodologies) cause problems ... How those who do work within the methodological framework are valued. It can't hurt to drop a seed or two since you may be re-visiting the same potential employer. This time he will be asking the questions, so it won't hurt to have some of the answers he is looking for! :)

OH!!! And always end any interview by asking, "If you were in my shoes, what questions would you ask (and why)?"

thnxx

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.