Tag Info

New answers tagged

-2

I tend to offer this when asked:- A PBI, or Story is something more than one person can get around. A Tasks is something only one person can pickup.


1

Scrum is only a start point for your process, look at it, keep the bits you like, ditch the bits you don't. It is NOT a religion, (despite many people's insistence on adhering to its holy scriptures). So, bearing in mind this, the point of Agile as a whole is to remove impediments (like management processes) to enable you to perform your work as easily as ...


6

"shippable" doesn't necessarily mean "usable by the end user", and it doesn't necessarily mean you actually ship it. All it means is that you're done writing and testing the code, and that it has an appropriate level of quality. With that in mind, you need to break down your epics into stories that can be completed in the context of a single sprint. Perhaps ...


4

Agile focuses on value (a.k.a. "solving problems for someone") Does this refactoring bring value? If not, or if you can't point your finger on it, then you have two alternatives: go back to the drawing board and try to understand exactly what problem you are trying to solve with this, or simply do not use agile for something with such a fixed scope and ...


0

Maintain the same team but different branches in your SCM. Your generation N product will generally be more stable so you should get (cherrypick) the stable code or any relevant improvements from branch N to N+1. Have the same developers who worked on feature X in product N work on the same feature in product N+1. That way they will be familiar with both ...


1

You could go with the two team approach and reduce the negative impacts by: allowing developers to work in both teams when it makes sense to swap the team resources around documenting and presenting research work to developers in the production team to allow them to raise any concerns or highlight things that the research team are not aware of, maybe put ...


2

It sounds like you're thinking about what a project is differently to how most of this kind of software does. As a result, you're also breaking down other pieces differently. In a tool like Jira: A project is an entire piece of software - a product. So in your case, you have one project. Modules within a piece of software are called components. In your ...


0

Think of it like this, what is the point of the daily stand up? It is your opportunity to raise impediments with the rest of the team, to flag up that you may need assistance, and to highlight changes that will affect others. It is important that you as a developer are there. With a team of 4 -8 developers, they need to be quick and snappy - 30 seconds ...


0

To avoid overtime, you have to cut the scope of the project. The following chart shows where uncertainty lies in a project: If you notice, at the product definition and requirements phases, you have a huge variance in estimation of effort. You can't be sure if it will take a month or a day to implement the feature. I'm betting that none of the tasks are ...


1

People over process. That's one of the core tenants of Agile, if a process isn't working for your team, scrap it or modify it. Let the team modify it to fit their needs.


1

I would recommend having your development team try to take on the role of user acceptance testing, at least to the extent possible. It may not be as effective as the actual users, at least until the developers have a strong understanding of the domain and how the users carry out their work in the software, but it will help catch the big things before you get ...


0

The first question to ask is What does a Story Point mean? If you define a story point as "How much work engineering gets done", then any answer will do. However if you define a story point as "How much value is delivered to the business", then it becomes important to not give credit until a story is 100% completed, accepted and delivered 100%. Modifying ...



Top 50 recent answers are included