How does agile communication differ from tradition software
engineering communication? How it is similar?
Answer Posted / sevak.yatrik777
Agile communication is quicker than traditional software
development communication in the following ways:
First, the project teams are "co-located" so that any
questions are immediately answered instead of using phones,
email, etc to ask coworkers for ideas, thoughts or answers.
Every day an Agile team meets for a quick 15 minute meeting
(sometimes called a daily scrum) to refine what tasks were
completed the previous day, what will be done by the team
today and what impediments are prohibiting the team from
getting the work done.
Agile teams are constantly refining scope based on empirical
data from previous releases, test results and discoveries
where traditional projects design and code up to the
delivery date only to discover problems when it's very
expensive to correct.
| Is This Answer Correct ? | 12 Yes | 6 No |
Post New Answer View All Answers
Can anyone send me e commerce website test cases please its urgent
Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?
what is the difference configurable items and non configurable items ?
Why is it that a single, all – encompassing metric cannot be developed for programme complexity or programme quality?
Hi I want to test regarding cookies.. Session should be good for 4 hours and once expired user is returned to login page.. How can i test the session is good for 4 hrs?? Whether i need wait for 4 hours?
explain the basic QA plan to co-op with development plan for effective delivery of the product
Why should an organisation be concerned about software risk factors and software quality?
all sap abap ale (idoc) interview questions
What are ‘throwaway’ prototypes and ‘evolutionary’ prototypes? How can production of a prototype be controlled and why is this important?
Explain the architecture diagram of your current project?
How would you do an Estimation?
what are the priliminary expectations from smoke testing from developer and QA point of view
As soon as you get a build ,what would you ask your testing team to do?
what are the usual metrics one have to apply for SW improvement projects
what are the basic artifacts required for QA from development teams start qualification