agile

I'm trying to work in a more organised way and started adopting user stories. I think I have misunderstanding of how should I use user stories for technical stuff. Let's say I'm coding an app that gives me the ranking of my site for a certain Keyword in Google. The user story goes like that: As an Internet Marketer I want to find out where my website ranks for a keyword So I'll know whether my SEO efforts work Now this is pretty straight forward and user centric... However, what happens if I need to introduce Proxies into the loop. On one hand, Proxies are technical implementation detail on

Closed . This question needs details or clarity. It is not currently accepting answers. Learn more . Want to improve this question? Add details and clarify the problem by editing this post . How a newbie differentiate between this? How one can know he/she is working is back-end system or front-end system? "Front-end" typically means the parts of the project a user interacts with--such as the graphical user interface or command line. It's a vague term, there isn't an exact definition. "Back-end" means the parts that do the work, but the user is unaware of or cannot see. Databases, services, etc

Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Currently, we're using the following version numbering scheme for our C# winforms project: "Major Release"."Minor Release"."Iteration Number"."Build Number within that Iteration" We wanted to be able to identify the iteration number and the build number within that iteration just by looking at the version number. In the past, we had done something like:"Major Release"."Minor Release"

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. I'm time+cost estimating a semi-complex software solution, that hasn't got specific requirements in about 75% of features. I would still like to make as good estimate as possible, by getting additional data from the client. There will still be parts that may end up not being able to develop, since there's too many dependencies with other products/technologies and lack of definition. I also have a very tight schedule to

Enough detail is enough is the usual response. On the project we are currently busy with (which was incomplete and handed over to us without any brs/documentation/user stories of any sort, we get stories like: As a Product Owner I need the developer to test the XXX workflow so that it works correctly. and As a Product Owner I need the developer to test the YYY workflow so that it works correctly. No indication is given of what "correctly" means. When asking for more detail, one is informed that you are asking for too much detail and since this is agile, the requirement will become clearer

Developers can learn a lot from other industries. As a thought exercise, is it possible to build a passenger aircraft using agile techniques? Forgetting cost for now; how feasible is it to use iterative and incremental development for both the hardware (fuselage, wings, etc) as well as software, and still come out with a working and safe product which meets the customer’s requirements at the time of delivery? Does it make sense to refactor a plane? I'm going to say "kind of". In fact there's one example right now that I think is pretty close to answering this question. Boeing is attempting to