Requesting quality analysis test cases up front of implementation/change
Recently I have been assigned to work on a major requirement that falls between a change request and an improvement. The previous implementation was done (badly) by a senior developer that left the company and did so without leaving a trace of documentation.
Here were my initial steps to approach this problem:
Is Agile a variant of RAD?
Wikipedia says that Agile is a type of “RAD” which I guess is incorrect. From what I know, Agile was developed becasue RAD itself was not that sucessfull in 90’S (too rigid for changes).
Or am I wrong?
What is Developer Anarchy?
I’ve been reading about Developer (or Programmer) Anarchy, which seems to be billed as a post-Agile development methodology. I found a few resources on it (1, 2) but it doesn’t seem to be a lot out there.
Handling unexpected features during sprint
Our team is going to adopt scrum and agile technics. We’ve got a product, which we develop for multiple customers. This customers supplied us with necessary requirements, so everithing is fine to adopt agile techinics.
Does the use of personas in Agile have any value during implementation?
This is about the use of personas, primarily in the agile development realm.
Why do we use story points instead of man days when estimating user stories?
In agile methodologies (e.g. SCRUM), the complexity/effort needed for user stories are measured in Story points. Story points are used to calculate how many user stories a team can take in an iteration.
Relationship between user story, feature, and epic?
As someone who’s still new to agile, I’m not sure I completely understand the relationship or difference between user story, feature, and epic.
How should we draw the release burndown chart?
I have been in various Agile projects and seen many release burndown chart styles. Most of them were handled manually since somehow all the tools that I have run across don’t produce really useful burndown charts.
Pair programming when driver and observer have different skill level and experience
I know pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer, reviews each line of code as it is typed in.
Dilemma of QA vs. iterations
In my company, we successfully working with agile practices – but without using iterations. The main reason is that we can’t find a clean way to fit in QA in an iteration cycle.