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
hi can anyone provoide SRS for order processing system and intranet plz
Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?
what are the new trends / methodologies in QA for SW product testing
What are the negative test cases for water bottle?
How would you finalize the number of resources/testers needed for the testing in the estimation ?
How does development of software differ from that of hardware from a quality viewpoint?
Why should an organisation be concerned about software risk factors and software quality?
what are the expectations of QA from unit level testing
Explain your daily task as a Manager?
what are the priliminary expectations from smoke testing from developer and QA point of view
Can anyone send me e commerce website test cases please its urgent
Explain the deployment process?
what is regression testing, how effectively the QA lead / manager can implement this for product qualification
How would you do an Estimation?
How would you finalize on testcases in estimation? Say you have 200 requirements. How would you come up how many testcases you are going to write for each requirements?