Questions tagged [agile]
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
-3
votes
2answers
68 views
Identifying the Redundant Requirements in Scrum
I'm working on the research to resolve the Requirements conflicts in distributed Scrum where teams are distributed over multiple locations. I'm proposing a model that consists of five steps including ...
0
votes
2answers
66 views
Does the Scrum Guide Specify How Often to Release QA/Test Builds?
See https://www.scrumguides.org/scrum-guide.html
I've read through this several times and can't find anything about how often to do QA/Test builds during a sprint. There is a section called increment....
3
votes
5answers
262 views
Should a Product Owner be responsible for an initial prototype?
Is it typical that a Product Owner (or even a BA) creates a high-level prototype/wireframe of a system based on the requirements document to ensure that the requirements are clear enough to start ...
4
votes
3answers
460 views
What exactly is Yak Shaving?
This came up when a developer brought in these planning poker cards, one of which is Yak Shaving.
There are various articles on google/wikitionary which basically say:
Yak shaving is programming ...
1
vote
3answers
188 views
Agile scrum - estimate another team's sprint
I heard a case where two teams are planning each others' sprints (estmating stories and deciding what goes into the sprint). The stated benefit is to solve one of the two team's problem with not ...
0
votes
1answer
64 views
should we consider a feature set as a microservice in FDD?
We are designing the software based on the FDD (feature driven development). Our architecture is microservice. I want to know that microservices are demonstrated by the feature set? In other words, is ...
1
vote
0answers
69 views
Reducing dependencies between stories & which branch (GIT) should QA's test on?
Background
We have a team of 8 devs and 1 QA (tester) and we're struggling with dependencies between tickets and causing a lot of merge headaches and/or people waiting around for the next bit of work ...
10
votes
4answers
419 views
Is deciding the release date before collecting all requirements un-agile?
I have just started reading the book Applying UML and Patterns by Craig Larman. I find it very interesting because it challenges many of what I have been told at work. I read that requirements aren't ...
8
votes
2answers
216 views
Does this count as a user story for a basic Sudoku game?
I am trying to make a user story for a basic Sudoku game, using the agile software development approach.
I get the concept behind user stories, but I was just wondering if it was possible to get an ...
1
vote
4answers
159 views
How to efficiently handle a scrum project when part of development team are from external firm?
In my organisation for one of the project we follow Agile Scrum methodology and following is distribution of the man power for the project:
Scrum Team:
SM
ProxyDev1(Internal): 50% in the project
...
4
votes
3answers
210 views
When is it reasonable to register an activity on the SCRUM board and when it is not necessary?
In my work we use the scrum board for the registration of activities, however there is always a dilemma of what to register there, some colleagues want to register on the scrum board the email answer (...
2
votes
2answers
151 views
TDD how to avoid test duplication across team
Our team has decided to develop using BDD/TDD in an effort to become the Agile team we're supposed to be. Vertical slicing appears to be an important part of agile working and gaining the quick ...
4
votes
4answers
290 views
If story points are about time, what is truly the benefit of using them?
Quoting the known Mike Cohn:
The primary reason for estimating product backlog items is so that
predictions can be made about how much functionality can be delivered
by what date. If we want to ...
28
votes
6answers
6k views
Does Scrum create additional overhead for projects where requirements don't change?
I'm reading the Scrum - A Pocket Guide by Gunther Verheyen and it says:
The Chaos report of 2011 by the Standish Group marks a turning point. Extensive research was done in comparing traditional ...
-2
votes
2answers
141 views
How many hours a day in a sprint in scrum framework?
I am trying to follow scrum framework as much as i can but i am facing some confusion. I like to know what are the standard guide lines for a sprint. I am designing the sprint but i am not sure to get ...
2
votes
2answers
92 views
Is it normal to retest the entire sprint before pushing to UAT
I have <5 years experience in the software industry and this is my first time doing QA.
Before the stories in a sprint move to UAT, I am supposed to retest every single story in ~1 day in an ...
-2
votes
1answer
64 views
Does the Product Backlog just consists out of User Stories in Agile Development? [closed]
As far as we know, the User Stories are the way a requirement is defined in bounded context with acceptance criteria. On the other hand, the Product Backlog enlists all requirements, i.e., new feature,...
8
votes
5answers
420 views
Do Story Point sizes for repetitive tasks change after you automate the task?
Here's the Scrum situation:
A certain task (implement a back end populated data table) is a frequent story
The tables frequently have similar but custom functionality
Each table takes about a week to ...
2
votes
6answers
190 views
Does it make sense to draw business processes when designing a software solution
We are working with the design of the software. It is piece already working developed from scratch again. My managers are telling me to draw the business processes. I doubt in this due the fact that ...
8
votes
4answers
447 views
Does every member of an agile team need to be a software developer?
We recently started using agile methodologies at my company. Because I am quite new to agile, I wonder if our way of implementing it is correct according to the basic principles of agile.
Previously, ...
2
votes
2answers
61 views
Whom does the Nexus Sprint Backlog belong to?
The Nexus Guide states that:
A Nexus Sprint Backlog is the composite of Product Backlog items from the Sprint Backlogs of the individual Scrum Teams.
However, trying to build an analogy between ...
0
votes
2answers
74 views
Reserved user story points
In scrum, do you reserve any extra story points for tasks that weren't part of the original estimate, but my come in between the sprint like any technical dependencies?
2
votes
2answers
80 views
Sprint planning: who decides which items of the Product backlog to be included into the Sprint backlog?
I am confused about the two following statements and how do they both influence on which items be included into the Sprint backlog:
The Sprint Goal and Sprint plan is produced by the collaborative ...
0
votes
1answer
30 views
“Materialised” view of the Sprint Goal and consequences of its absence
The Scrum guide defines the Sprint Goal as:
an objective that will be met within the Sprint
through the implementation of the Product Backlog, and it provides
guidance to the Development Team ...
7
votes
5answers
434 views
Should we be documenting our Scrum Retrospective feedback before the Retrospective meeting?
Our Scrum master wants us to document our feedback for the iteration before our Retrospective. Her argument is that she wants us to have time to document our feedback. Another guy on the thinks that ...
0
votes
3answers
61 views
Where does 'doc specifications' end and 'role ownership' start?
What is the Agile philosophy around the criteria for a groomed story and Tech team responsibility?
(I deliberately phrased the explanation as antagonistic for the sake clarifying the opposing ...
5
votes
2answers
259 views
When are component teams a better choice than feature teams in agile development?
When it comes to organizational structure in an agile context, many people claim that feature teams are generally a better choice than component teams. This at least is what I find when discussing ...
0
votes
2answers
154 views
How to keep CRUD user stories from being trite and simplistic?
I'm having trouble keeping my user stories for basic operations from sounding ... basic. For example, suppose I'm building a CRM to keep track of clients:
C: As a user, I want to create a client, so ...
12
votes
2answers
2k views
A definition of “Done” in case of several Development Teams working on a same product
One of the scrum tests contains the question about the definition best describing "Done" when multiple development teams perform a work on a same product.
A proper answer states that those ...
14
votes
3answers
4k views
How to affect priorities to bugs to developers and treat them accordingly?
We have a bug process that is currently being worked.
We have 3 levels of bug:
P1 bug: Bugs that prevents users from working. They must be solved on the spot.
P2 bug: Bugs that are impacting but ...
-2
votes
1answer
76 views
How to alleviate the development process through JIRA?
In our agile-scrum process, for each epic we are creating , we are creating automatically one user story that is related to that epic.
From that user story, we are creating automatically too, 4 ...
1
vote
2answers
55 views
Additional Stories in sprint for quick fixes
I have introduced sprint into our team and after a rocky start, we are starting to get some rhythm. One of the opinions of the dev team is they still want to be able to work on bugs and enhancements ...
1
vote
1answer
107 views
Why are burn down and burn up charts mostly used in agile projects?
Burn down and burn up charts are used in agile projects to visualize the progress of a sprint. The same type of chart could also be applied to entire projects, not only to a single sprint. Thus they ...
0
votes
2answers
69 views
How to Integrate Old UI in Microservice
We have about 10 applications in one Monolith that need to be refactored into Microservices.
Following an Agile approach, we would like to split work into vertical slices where each slice would be ...
-2
votes
1answer
101 views
Is there any good reason for not using the issue tracker 'properly'?
I am used to treating the issue tracker as a source of truth and an organisational memory. I use it to record what the issue is and what has been done towards resolving it.
I consider this to be ...
1
vote
3answers
178 views
how would you plan monthly refactoring days to eliminate technical debt in your team?
My team (yet) did not do much to work on technical debt and our code base includes huge amount of TODO code, unused code, 'could get better' code, @Ignore unitests and more.
I am about to start ...
0
votes
2answers
249 views
How do squads work in the Spotify engineering model if they share the same code repository?
The Spotify model has become a popular example for the right way of doing development.
If a product has a single, main, code repository, like most products have, how do you make squads autonomous and ...
1
vote
3answers
289 views
Normalizing story points across teams, is there a big problem?
We have been thinking about comparing product size/effort at least roughly and this is what some suggested:
There are multiple products, each with one scrum team
All the scrum teams estimate their ...
2
votes
4answers
442 views
dev and qa in same sprint
I am not the first one to ask this but i also did not get anything concrete from other such posts to tell me what is needed so i am posing the question here. Feel free to refer to some other resource.
...
-3
votes
2answers
183 views
Why are all definitions of agile framework so handwave-y?
Take the wikipedia definition:
Agile software development is an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing ...
0
votes
6answers
244 views
Should agile sprints/iterations be back-to-back?
I know -- it depends, right?
What I'm asking is whether the notion that sprints/iterations in agile development should always be back-to-back, with only a review and planning meeting to separate them ...
54
votes
11answers
10k views
Agile Practices: Code Review - Fail the review or raise an issue?
At the end of a 2 week sprint and a task has a code review, in the review we discover a function that works, is readable, but it's quite long and has a few code smells. Easy refactor job.
Otherwise ...
2
votes
2answers
563 views
What is the difference between agile and incremental development process models
As the title implies , what is the difference between these both concepts? According to my understanding , Agile software process uses increments , where some requirements are first implemented and ...
0
votes
3answers
101 views
How minimum-documentation agile development is compatible with requirement that business processes should be documented?
Minimum-documentation is one of the basic features of agile development (intuitive GUI, visually rich documentation, automated tests replaces it). But usually software development goes hand in hand ...
1
vote
2answers
106 views
Can story points be used to describe size of several projects estimated by several teams?
KLOC has been - I think justly - criticized as too inaccurate to express size when comparing several projects.
In only one source I found a calculation that uses Story Points and thus allow to compare ...
-1
votes
1answer
40 views
Verification Statements and Acceptance Criteria
We are using verification statements which describe how the requirement should be tested. These statements are co located and associated with the requirement. How is this different than a set of ...
1
vote
1answer
139 views
Preexisting culture issues during Scrum transition
My team has been trying to transition to Scrum for some time now, but it seems like the preexisting culture is preventing the team from switching to a new mindset or even causing it to move in the ...
3
votes
4answers
219 views
User Story Time Constraints
My team has been trying to switch to Agile recently. The line manager has been taking 1-2 days per user story as a hard limit rather than a guideline, and framing it as a failure of the developer if ...
2
votes
4answers
224 views
Only test when necessary in agile software development: good or bad idea?
When taking an agile development approach, it is obvious to only implement features when necessary. My question is: can the same be applied when it comes to testing, i.e. creating test cases and only ...
-1
votes
2answers
162 views
Are agile (and other software development process/methodologies) really bad for architecture and design?
I was wandering around google and saw a paper in which the author says in introduction that Agile methodologies, (in my own word) does not put enough emphasis on software architecture and design...
...
