In a team practicing Domain Driven Design, should the whole team participate in Stakeholder meetings?
In my experience, a Software Development Team that comprises:
Why has extreme programming (XP) gone out of date in favor of Agile, Kanban etc?
I like XP (extreme programming), especially the part where there are 2 programmers at the same screen, since a problem’s solution is often found more quickly if only you explain what you’re doing and pair programming forces you to explain what you’re doing.
Native mobile app development – how do I structure my user stories?
I’m about to start on a project which will involve developing prototype native mobile apps (iOS and Android initially) as well as a web-based admin interface and an API for these apps to communicate with. We’ve got a list of stories already drafted up, however a lot of them are in the format:
How to learn & introduce scrum in small startup? [closed]
Closed 6 years ago.
Pair programming and unit testing
My team follows the Scrum development cycle. We have received feedback that our unit testing coverage is not very good.
Can an internally developed fast evolving, agile, short sprint web application lend itself to offshoring?
I have recently been set a target to achieve readiness to successfully manage and deliver results through the usage of offshore teams on our mainline development project within 12 months.
What to do when there are no logical user stories but separate development tasks?
We need to generate a release in 3 weeks, and for the planning we are doing today we don’t have coherent logical user stories from the backlog tasks. Is valid to match say each development task is equivalent to an user story?
Using Completed User Stories to Estimate Future User Stories
In Scrum/Agile, the complexity of a user story can be estimated in story points. After completing some user stories, a programmer or team of programmers can use those experiences to better estimate how much time it might take to complete a future user story.
What methods of requirements elicitation are suitable when I do not have direct access to the user base?
I am working on an application to create invoices. There are some features that are required based on the type of the application and are common to all invoice applications. However, we still need to determine what unique needs the user base might have. We do not have direct access to the users to obtain requirements or user stories. What techniques are most suitable for eliciting high-quality requirements from users when direct or frequent access is not possible?
What methods of requirements elicitation are suitable when I do not have direct access to the user base?
I am working on an application to create invoices. There are some features that are required based on the type of the application and are common to all invoice applications. However, we still need to determine what unique needs the user base might have. We do not have direct access to the users to obtain requirements or user stories. What techniques are most suitable for eliciting high-quality requirements from users when direct or frequent access is not possible?