Interviews are my favorite part of the process because we finally get to meet you in person. Interviews will occur between mid-October and mid-November. In addition to on-campus interviews, we also conduct interviews in Shanghai, Tokyo, Dubai, Mumbai, São Paulo, New York City, Bay Area CA, London, and Paris. Where you interview does NOT affect your likelihood to be accepted (all interviews globally are conducted only by members of the Admissions Board). Choose what’s most convenient for you, and if you aren’t able to travel, we will work something out via Skype.
Thank you Rajeev. I took coaching there jus after i finished engineering in 2011. But, it was only helpful wrt the fact that i came to know which books to study from etc. i found itvery very basic, although views may differ from person to person. I am glad that these days sites like insights, ias baba n mrunal etc already have ample guidance on which books and previous questions. so I think coaching is not some mandatory thing, specially for a subject like history. Make sure you start prep with new ncerts 6-12 and ignou ba material. Then, you can refer to other books. At best you can buy hemant jha sir and baliyan sir’s notes to get an idea if you are not missing on something. best wishes
Smaller requirements are easier to estimate. Shall statements, such as “the system shall convert feet to meters”, are an example of very small requirements. User stories are a little larger but still relatively easy to estimate. Use cases , a staple of the Rational Unified Process (RUP) and the Agile Unified Process (AUP) , can become too large to estimate effectively although you can reorganize them into smaller and more manageable artifacts if you're flexible. A good rule of thumb is that a requirement must be implementable within a single iteration. Scrum teams usually have month long iterations whereas XP teams often choose one or two weeks as an iteration length. Short iterations reduce the feedback cycle making it easier to stay on track. Successful teams will deploy a working copy of their system at the end of each iteration into a demo environment where their potential stakeholders have access to it. This provides another opportunity for feedback, often generating new or improved requirements, and shows stakeholders that the team is making progress and thus their money is being invested wisely.