![]() ![]() If they won't prioritize what they want, you are going to struggle. The idea is that if you run out of time and something doesn't get done, it should be the lowest priority items. There's no sense in killing yourself over something that was really a nice-to-have. You should be doing things in the order of the priority set by the product owner (or customer). What is the best practice way to handle multiple spikes when they are basically non-negotiable requirements of a project? If not, wouldn't the total project schedule be at the mercy of one of these spikes coming back with data that this particular story will take way longer than we ballparked? The project involves three things that nobody on the team has any experience with: Integrate with the Foo Payroll System, be able to handle the file type XYZ89 (where "XYZ89" = some file type you've never heard of), and convert some other files so they can be handled by the Frobnobdicator.Īs I understand it, standard Agile practice would be to schedule spikes for each of these, after which we can determine how long they're going to take (I'm not sure there's much of a chance that the client will decide not to do them, as they're pretty much solid requirements of the project)ĭo we do all the spikes up front in the first iteration to get a better estimate of the time it's going to take to do them and/or get a "walking skeleton" up and running? we can probably just grab an agile book and follow it like a recipe), with one bit of confusion: Team is starting on their first capital-A Agile project, and the project seems like it will fall in line nicely with the methodology (i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |