network profile
|
Jun 9 |
accepted | How would you get all your expectations done within a user story? |
|
Jun 6 |
awarded | Enlightened |
|
Jun 6 |
awarded | Nice Answer |
|
Jun 5 |
awarded | Yearling |
|
Jun 5 |
awarded | Citizen Patrol |
|
Jun 5 |
answered | Which is architecturally correct for Data Access Layer method names - Fetch or Select? |
|
Jun 5 |
awarded | Custodian |
|
Jun 5 |
awarded | Editor |
|
Jun 5 |
revised |
How would you get all your expectations done within a user story? edited title |
|
Jun 5 |
reviewed | Approve suggested edit on How would you get all your expectations done within a user story? |
|
Jun 5 |
awarded | Teacher |
|
Jun 5 |
answered | Is it bad programming practice to check if a class referenced by its interface is an instance of another class? |
|
Jun 5 |
asked | How would you get all your expectations done within a user story? |
|
Jun 27 |
comment |
Who should be the architect in an agile project? I accepted this as answer, because it showed me a bit what agile development should be and that it is not what we are practicing. The key part was that you have to welcome change. In a system where changes take too long it is not really welcomed. The main goal of agile development is good working code, not one and not the other. It is not to get user feedback. It is to understand the user feedback and craft that in the best results you are able to. The sad thing, many people think they are agile, but simply spoken, they are often not. Thanks to @RobertHarvey and Kyle Hodgson for your support. |
|
Jun 27 |
accepted | Who should be the architect in an agile project? |
|
Jun 26 |
awarded | Scholar |
|
Jun 26 |
accepted | How to define implementation details? |
|
Jun 26 |
comment |
Who should be the architect in an agile project? I understand what you are going to tell me, but I have to agree @RobertHarvey in his concerns about some major design decisions. Splitting up a repository into two or more smaller ones, is a huge impact on workflow.
There isn't the question wether I need it or not. I know I would need it, because of some reqirements, but I try to move out the decision to a later point.
If such major decisions are made upfront, you might save much time. |
|
Jun 26 |
comment |
Who should be the architect in an agile project? @Euphoric: Feedback is hard for that kind of software, because no one would ever see it. It will always be behind the scenes. Maybe agile is definitely the wrong practice. But, wouldn't you describe "Your code is messed up.", as user feedback too? Isn't technical excellence a goal of agile development? I could put all stuff into one assembly, one class, or I could split it up from beginning, as best as I can, thats part of my continious refactoring. There wouldn't be to much more effort, done right. |
|
Jun 26 |
comment |
Who should be the architect in an agile project? @RobertHarvey: Yes that's our problem, software quality is no requirement for the customer (our boss), but it would be one for me. I can't convince him that there is value behind the early investions necessary for high quality software. The team is waiting for a requirement to make maintainable software. So we might have a deadlock here. |
