Relative Content

Tag Archive for project-management

What is the standard term for my role?

I’m doing work that involves writing code and managing developers in a “special projects” division of a large company. I’d like to define my role better and figure out if there’s an industry standard term for what I do, so that it will be easier for me to research best practices and work on a career path

Where did the estimation rule of thumb originate that time spent will be one-third in each of the following: design, implementation, and testing?

I’m looking for a reference to the following. I commonly hear that one-third of a projects time will be spent in design, one-third in implementation, and one-third in testing. The three phases of development seems to be derived from the waterfall model. But, where did the time division originate (1/3, 1/3, 1/3)? Is there a paper or book that this is from?

How do bug reports factor in to a sprint?

I’ve been reading up on Scrum recently. From my understanding, a meeting is held before the sprint starts, to decide what gets moved from the product backlog to the upcoming sprint backlog. Once a feature is completed in the current sprint, it will go into the “Ready to QA” bucket, and it’s at this point that I’m getting confused. Do bug reports go back into the product backlog? I assume they can’t go back into the sprint backlog as we’ve already decided what work will be done for this cycle? What happens when QA finds a bug? Where does it go?

Is there some software to manage a XP Project? [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 […]

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.

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.