agile Questions

Unless I've misunderstood the principle, agile sprints are about layering on features until you arrive at some final release.  

But software can become unwieldy complex and choosing the right data structures and class patterns, for the application, is crucial - isn't it?  

So, how can you decide on the right data structures and classes and patterns, at the very beginning of the process, if in the first sprint, you are only dealing with a few of the overall application features?

Do you continually refactor and re-write as new feature-information is presented? Or is there some overall application design architecture happening up-front?

BTW, I'm not a formally-trained computer scientist, or software developer.

By Eric King - July 1, 20141 Answer

How do I submit an artilce?

 

Can You guys tell me the current trends /techniques that are followed in the test case Designing 

Agile was not working well in my current project, due to the requirements gap and short in resources. Is it be safe to go back to SDLC waterfal model to continue the project.

Is it possible to implement Lean principles in the ongoing Agile project?

Can you explain with a example? I believe that it may be possible to implement in personal activities.

what is the procedure to publish an article on AgileConnection

I would like to publish an article in this AgileConnection. Please let me know the procedure for it.

my emailid is [email protected]

I have a customer who is not mature in Agile. He is thinking of using agile methodology to migrate several open source collaborative software/platforms to a single identified platform.

His is thinking that migration team is ready to learn and carry out migration at the same time? Is tghis a good idea? Is there any case studies or tips on using agile methodologies for migration projects and which methodology?

 

Thanks in advance

In my research study, I need to identify the list of key features of user story management tools that can be used to support agile development. So far, I identified the following general groups of features: User role modeling and personas support, User stories and epics management, Acceptance testing support, High-level release planning, Low-level iteration planning, and Progress tracking. Each group contains some specific features, e.g., support for story points, writing of acceptance tests, etc.

Please help me elaborate the list by posting your list of such features, such as those that you've already used as part of a user story management tool, or those that you'd like to see in the software tool you use. Do you find some features more important than the others? Many thanks in advance! 

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.