meta user
network profile
| bio | website | |
|---|---|---|
| location | Guildford, United Kingdom | |
| age | ||
| visits | member for | 2 years |
| seen | Apr 23 at 21:13 | |
| stats | profile views | 11 |
|
May 16 |
awarded | Yearling |
|
Apr 4 |
comment |
Do your stories include tasks across disciplines? How do you do capacity planning? If your mockup is really complex, perhaps that's an argument for moving their design inside the agile process so that they are kept as simple and as close to the original problem as possible? |
|
Apr 4 |
comment |
Do your stories include tasks across disciplines? How do you do capacity planning? @nwinker I've worked with your second approach in the past. The problem I found was that there was a large backlog of pre-requisite work being done that was either wasted if the story was changed or never accepted, or created a pressure to accept a story because this work had been done. Does this happen with you? Like you say, Kanban might be better suited, and the more I've worked with it, the more I like it. |
|
Apr 4 |
answered | Do your stories include tasks across disciplines? How do you do capacity planning? |
|
Apr 4 |
comment |
Do your stories include tasks across disciplines? How do you do capacity planning? Separating stories into "Account Screen UI" and "Account Screen Dev" strikes me as a very bad idea. These aren't stories - they are tasks that are part of a story, but the story is either delivered or it isn't. A story delivers business value and what value to the customer is developing the wireframe? None at all. If you separate stories like this it makes it very difficult to prioritize them in order of business value since, as well as the issues of dependency that you mentioned, you simply cannot evaluate the value to the business of a task. |
|
Apr 4 |
answered | Logging to database: Log first or action first? |
|
Mar 26 |
awarded | Good Answer |
|
Mar 21 |
awarded | Nice Answer |
|
Mar 21 |
answered | Why do relational databases only accept SQL queries? |
|
Mar 20 |
answered | What problems can be solved using Generics? |
|
Feb 20 |
awarded | Nice Answer |
|
Feb 19 |
answered | Workflow for building a RESTful API |
|
Feb 19 |
comment |
Is it fair to ask a team to start using CoffeeScript? @YannisRizos So I'm going to add some BananaScript to the project, and Joe, the new guy, is going to use SomeMadeUpScript because he saw it once and it looked cool. Neither of us tell anyone, but it's fine because they are even easier to learn than CoffeeScript, so there will only be a small learning curve. ;-) Where do you draw the line? |
|
Feb 19 |
comment |
Is it fair to ask a team to start using CoffeeScript? @YannisRizos "The compiled output of CoffeeScript" is not what you're asking your fellow developers to maintain. It's the source CoffeeScript. |
|
Feb 19 |
answered | Is it fair to ask a team to start using CoffeeScript? |
|
Feb 13 |
awarded | Nice Answer |
|
Oct 5 |
comment |
Automated unit testing, integration testing or acceptance testing I'd just like to add a belated link to JB Rainsberger's Integration Tests Are A Scam. It highlights many of the reasons integration tests are a false economy. |
|
Oct 1 |
awarded | Commentator |
|
Sep 25 |
comment |
Is agile about development or management? @pdr Well he's definitely agile, he just doesn't follow any agile development process that we would adhere to. But perhaps it's more talking about "Agile" the noun, i.e. the process that's a bit like Scrum, that irks me most. |
|
Sep 25 |
comment |
Is agile about development or management? Am I the only one who doesn't think "agile" should have a capital letter? I'm not just being a grammatical pedant - it's important. Understand agility as a quality: if your team is agile, it is flexible, adaptable, methodical. I always find confusion starts when they talk about "Agile" as if it's the name of a standard pattern or process to which they must adhere. |
