Being a team manager and a developer in a Scrum team
I am managing a team of 6 people that recently moved to Scrum.
User Stories with design elements in Scrum
We’re implementing a Scrum workflow and I’m trying to wrap my head around user stories, when they’re completed, iterations, etc. One thing we often do is work on a story during an early iteration, get it fully working but “ugly”. We use plain buttons, no images, just the text to show that it’s working the way they should. We show our customer, make sure they are happy with how it’s working, then we usually use images they provide to finish up the design of the feature and complete it.
What relationship do software Scrum or Lean have to industrial engineering concepts like theory of constraints?
In Scrum, work is delivered to customers through a series of sprints in which project work is time boxed to a fixed number of days or weeks, usually 30 days. In lean software development, the goal is to deliver as soon as possible, permitting early feedback for the next iteration.
What makes for a good architect/manager/lead developer?
I am the Lead Developer for a small software company. Over the past two years, my team has grown from one developer (me) to a group of about nine people. Most of us are very capable, senior engineers (20+ years of experience building software per person), so very little hand-holding is generally necessary. We use Scrum to manage our efforts, and we usually get a lot done quickly with minimal written requirements.
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).
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 […]