As a non coder (Score: 2, Interesting) by zafiro17@pipedot.org on 2014-10-13 20:11 (#2T8B) As a non-coder, this is all fascinating to me. I read all the wikipedia pages (thankx Bryan). As a project manager though, it seems to me like different versions of really elementary stuff:1. Let's talk to the client to make sure we know what we want,2. making sure the client also knows what that will entail in terms of hours, money, effort.3. then let's stay in touch as we go in case the goals or demands shift.After that it's just a matter of: Do you go section by section? Do you start with a prototype and then work outward? Do you finish the first section/module/unit/whatever before starting the next one?Basic project management, I think. Is there more to it than that? Re: As a non coder (Score: 1) by genx@pipedot.org on 2014-10-20 00:41 (#2TG9) There is more: when a method requires you do steps A, B, C in order, you can do step A and then step C, and, when it is over, do step B (or just pretend that you have done it) because your boss told you to follow that step order or because you have to fulfil a norm that requires this method. With all the various methods there are now, you can invent infinite ways of getting around them. This is what is most rich and powerful about development methods :->
Re: As a non coder (Score: 1) by genx@pipedot.org on 2014-10-20 00:41 (#2TG9) There is more: when a method requires you do steps A, B, C in order, you can do step A and then step C, and, when it is over, do step B (or just pretend that you have done it) because your boss told you to follow that step order or because you have to fulfil a norm that requires this method. With all the various methods there are now, you can invent infinite ways of getting around them. This is what is most rich and powerful about development methods :->