Geek Answers Handbook

Agile Scenario, what's right?

Imagine that you have a user 1 story that requires an implementation of a method:

public static void MyMethod(string paramA);

Several classes will use this method, and MyMethod does everything necessary to complete the history of user 1, but nothing more.

Are you sure that in the future iteration another story will come (user story 2), which will require the method to become:

public static void MyMethod(string paramA, int paramB);

Previous calls to MyMethod will need to be reorganized, and some new calls to MyMethod will need to be added in accordance with the requirements of user story 2 (Note after story 2 it never makes sense to call MyMethod only with paramA).

When working on user story 1, this is flexible thinking:

1) Only implement: public void MyMethod (string paramA);

2) : public void MyMethod ( paramA, int paramB); - . 0 .

3) : public void MyMethod ( paramA, int paramB); - . ( 2)

4) : public void MyMethod ( paramA, int paramB); - , 1 2

+5
5

Agile purists, , . - Big-Design-Up-Front, , , . , , . , , - . , 1 2 . S2 , ? S1 - " ", S2 - "", S2, . "Have-to-have", . , , , (# 3).

, S1 S2 , Backlog. , , , Agile-, S2 . , (?), S1 S2, 1 . .

+2

1.

, - .

, , , 2 , , 2, . , .

+12

1, , 100% , , .

HOWEVER Agile , , , 1, .

+1

" ". , , .

, , , . , . ? , . " ..." . , , , , . .

, , " ", , . , , - , . . , , .

+1

. , -, , , .

However ... Like all good questions, the answer is really "it depends." In some respects, your example is too trivial to pay tribute to the discussion. What if story A was “update client name” and some transactional function was added to story B (perhaps paramB is a TX context). In this case, maybe your stories need some work. Does A mean real meaning without B? Is A this morning and B during the day, or is it open during the next month?

0
source

More articles:


All Articles