Tag Info

New answers tagged

0

A Jira Kanban Project (out of the box) displays a field called "Epic Link" in each Story, Feature, Task, Defect or several other issue types. This is true of the both server and cloud versions. This lends itself to using Epic to mean a collection of stories. Stories and Features can also have sub-tasks assigned. Storys usually give some business value while ...


-1

Convincing mgmt to get away from the SRS and to start using user stories is essentially the same thing as convincing mgmt to adopt Agile. There are compelling statistics out there on the productivity benefits of Agile. One example is the presentation VersionOne gave at a 2013 conference. Show mgmt this industry data and if they are the listening type, you ...


0

When we started building our product, we also implemented Kanban, and along with that, we implemented a complete test automation strategy. As a result, today we don't have testers in our team. Instead, developers must write test cases and automate them as part of working on any user story, enhancement or defect. Our definition of Dev Complete includes ...


4

Yes, testing absolutely should be part of the definition of "Done". Without question. From a purely agile standpoint, the right approach is for everyone on the team to contribute toward writing tests. The tester would be the one coordinating the effort, but it is the responsibility of the entire team to make sure the software is properly tested.


5

Firstly, a ratio of 10:2 is bad. From experience, a ratio of 3:1 or 4:1 developers to testers works well. You'll likely need at least one more tester therefore, otherwise the testing backlog will grow and either never get cleared, or you're cut corners somewhere. If you test tasks in the next sprint, you are implementing mini-waterfall or "scrumfall" as you ...


5

This is fairly common, if not typical. To answer what are several questions: What should be the right approach to track activities in such scenarios? Will features get done without QA but with defects? How can I track the efforts seamlessly? Should testing be part of "Done Definition"? What are the pitfalls if it is not? I would take an overall ...


13

Feature ownership is inevitable, and done well can be a good thing. It help builds mastery and allows autonomy - two of the generally recognized pillars of engagement. It makes it clear who has the accountability for that code, and aids in delegation, communication, and otherwise getting shit done. But you're not talking about that. You're talking about ...


37

In my 20 years of experience, it is better to have code ownership rotate responsibilities amongst designers or at least have a pair of owners. Single feature ownership has the following issues, several of which you mentioned: it tends to pigeon hole designers and limit their growth opportunities it puts all the eggs in one basket so if someone is hit by a ...


0

The sponsors, developers, and users should be able to maintain a constant pace indefinitely. A sprint means... run at full speed over a short distance. Using the term sprint is still compatible with the (Agile) ability to maintain a constant pace. A whole group maintaining a constant pace does not necessarily mean that they are all moving at the ...


0

Any suggestions on how we get the team bought in to finishing the sprint by the end date? Strictly speaking, the Sprint is finished by the end date, whether the Sprint Team has completed all the Sprint Backlog items or not. You don't need "buy-in" to finish the Sprint on time... You need "buy-in" to actually follow Scrum. Why do we think it is ...


0

What is the recommended approach to fix this when we realize our error Estimates are estimates. I would not view it as something to be fixed, when it happens. I would view it as an opportunity to diagnose the reasons and improve your future estimates. Since the aim of Scrum is high quality increments of deliverable product, you want to stop and assess ...


0

At some point during each Sprint, you should have a Product Backlog Refinement Meeting. At this meeting, you ensure that the top portion of the Product Backlog is broken down sufficiently for items in that portion to be added to the next Sprint Backlog. If Product Backlog Refinement is managed well, then the Sprint Planning Meeting can be more efficient. ...


0

...how to plan the project so that my coding and implementation will start according to the delivered required web services? It sounds like you already do such planning, but that the customer sometimes delivers late or out of sequence. Should I consider using agile? Yes, you should consider "using agile". Whether or not you actually chose to adopt ...


1

While the question, as posed, has broad scope, the core issues seem to be: ...Scrum assumes that there is no 'requirements freeze'... ...embedded system due to tight coupling with hardware need upfront specification... Scrum aims to produce high quality increments of a deliverable solution. It does not aim to minimise re-work or minimize time to ...


0

While significant supporting motivation and explanation was provided, the core question seems to be: ...how do you make this work effectively when there is distance between the developers and the users? To me, this challenge is not unique to Scrum. Effective collaboration between geographically dispersed individuals is a common challenge. While the ...


1

Does the software team has any influence on the hardware specs? Or is it purely the other way around (hardware team dictates low-level software interface)? In the latter case, a HAL (hardware abstraction layer) person must sit with hardware team to write the low-level software interface; GUI team can work at their own pace, possibly using Scrum or any ...


1

I don't have personal direct experience in embedded systems - but I do understand waterfall and agile and the differences between the two, as I am sure you do too. I have also discussed this issue - of applying Agile in industries such as embedded software development, semiconductor design/ development, etc. with friends who work in those industries - so ...


1

Scrum is not concerned with requirements freezing or not. Scrum works equally well if you start with 100 stories in your backlog that never change, or 5 stories with more being added/changed all the time. Scrum is supposed to be an iterative process and it requires a totally different mindset than more traditional waterfall models. Technically with Scrum ...


1

If you are faced with the work needing to be re-done, you re-do it. Re-doing the implementation of a product backlog item does not necessarily require any user story to be re-written. The motivation to re-do the implementation may not have had anything to do with a change in the user story. Re-doing some implementation also does not necessarily require a ...



Top 50 recent answers are included