What is a “behavior rich object” and why would it be advantageous?
I am referring to the article Mocks aren’t Stubs by Martin Fowler. When naming cases when he think “mockist” TDD will be advantageous, he said
Story points for bug fixing tasks: Is it suitable for Scrum?
I’m just wondering if we should assign story points to bug fixing tasks or not. JIRA, our issues-tracking software, does not have story point field for Bug type issues (it’s only for Storys and Epics).
What’s a good model for continuous manager programmer feedback?
Is it important for managers to give devs regular feedback on how they’re doing and vice versa? I say vice versa because I consider employees to be responsible to their manager, and managers to be responsible to their employees. Everyone seems to think this is a good idea but in practice I rarely see it happen because so many shops are “agile” now and that usually means a daily standup plus a weekly kickoff, etc. So one-on-ones just don’t happen.
Design documents as part of Agile
At my workplace, we face a challenge in that “agile” too often has meant “vague requirements, bad acceptance criteria, good luck!” We’re trying to address that, as a general improvement effort.
Branching and CI Builds with Agile
We follow many agile processes, including automated tests, continuous integration, sprint reviews, etc… We’re currently having a debate about how often we should branch release builds.
Is it a good practice to have Epics under User Stories?
In my current team there is a practice of putting Epics under User Stories and sometimes even User Stories or Epics under Tasks! When questioned, the usual reply is: “if it is not a good practice then the project management tool would not have allowed doing so!” (IBM Rational Team Concert, for one does not prevent such practice.)
Do story points have a direct relation with task estimates?
In my current team, where we run multiple scrums, the Story points are usually based on the effort required to complete the User Story. For example if an User Story has 2 tasks, both needing 5 days each, they the Story is assigned 10 points. So 1 day of effort is considered to be one Story point.
How to adopt scrum agile methodology for a small .Net team [closed]
Closed 12 years ago.
What ‘s the essential difference between agile developing and plan based developing?
In agile process, the product owner put the unformal ideas/user story/backlog items to the sprint/iteration. Sprint/iteration is like a plan for a short term and it is drived by daily meeting. Planning is made in both processes. So what’s the difference between agile and the old plan based developing?
Software Management Tools for Agile Process Development [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]