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
I am looking for interview question / technical questions for veritas netbackup.
hi can anyone provoide SRS for order processing system and intranet plz
explain the model(s) of co-ordination you experienced for effective delivery of the product
How would you do an Estimation?
Why should an organisation be concerned about software risk factors and software quality?
As soon as you get a build ,what would you ask your testing team to do?
How to write testcases while we know only the datatypes for the fields
brief about the methodologies to evaluate weightage of test cases and what are the basic parameters to be considered
What are ‘throwaway’ prototypes and ‘evolutionary’ prototypes? How can production of a prototype be controlled and why is this important?
what are the basic artifacts required for QA from development teams start qualification
what is the difference between testing and quality analysis
How does development of software differ from that of hardware from a quality viewpoint?
Give a suitable definition of software quality and briefly describe the rationale for your definition.
What kind of Reporting you do?
what are the priliminary expectations from smoke testing from developer and QA point of view