Rewriting software using Agile methodologies
Suppose you have to rewrite an entire application using Agile methodologies, how would you do it?
Solutions for Project management [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 […]
Should you ever re-estimate user stories?
My current project is having a ‘discussion’ which is split down the middle- “this story is more complex than we originally thought, we should re-estimate” vs “you should never re-estimate as you only ever estimate up and never down”.
Should the number of developers be considered when estimating a task?
I am pretty inexperienced with working in agile projects but I have tried it a few times and I always run into this problem when estimating a task.
How to manage product backlog/user stories
We’re about to start a new project using Agile (using TFS), and I have a couple of “good practice” questions regarding the product backlog:-
Agile product backlogs
We are starting an Agile project, and the product owner has made a start adding user stories to the product backlog (mostly epics at this stage).
What level/format of access should be given to a client to the issue tracking system?
So, I used to think that it would be a good idea to give the customer access to the issue tracking system, but now I’ve seen that it creates less than ideal situations, like:
Is there a study showing which agile approach is best suited for particular kind of project? (in this case a re-platforming project, Java to .NET)
It is said that the Kanban methodology is suited for software maintenance and support areas, whereas Scrum is more suited for new product development. No process or methods are complete. Using the right one will help you succeed, but they will not guarantee success.
Agile project management, agile development: early integration
I believe that agile works if everything is agile.
Is it appropriate to run a complex enterprise-system configuration and migration project in a similar way to a Scrum development project?
I’m just starting out on the implementation of a large enterprise-wide system, which has complex requirements and many stakeholders.