Sin título

Página 1

Agile idea to write a testable user stories

Use retrospective to improve the approach in agile projects

Communicate effectively, interact and proactive feedback and working closely with business and other development team numbers

Whole team approach

We accept and embrace change

We don't believe in documentation

We believe in working software than comprehensive documentation

'just enough' documentation

knowledge not happening verbally that is we feel the need for documentation

what Is the best suitable method to convey information to and within the development team is face to the face conversation

The team should have BEST architecture, requirements and design emerge from self-organising team Chowdary9717

What are the challenges while working in development

distributed development

Ambiguity in "Definition of done"

we have 12 agile principles

Good design techniques

stand up

Communication and collaboration

User stories just enough for planning and estimation not enough for the features to be developed and tested

potential go-to guys in an agile team

Agile lead

development team

database admin

Network admin

infrastructure expert

user experience

The tester should write integration tests for the developer's actions

advantages of the agile way of development

less chance of misunderstanding on requirements

identify the defect and bugs early

quality is a team goal

Aspects of agile approaches