New answers tagged

0

I agree with most of what @Bogdan wrote but want to address those changes that do impact project constraints but are caused by both random or non random drivers that are out of control for everyone. In my opinion, the change process, which would be documented in the change log, should be reserved for formal changes to scope, budget, and schedule. The ...


1

A change log is the place where you record changes to the project. This regards changes that weren't initially planned or included by the project's constraints of (mainly) cost, scope and time. The change log is something from traditional project management, which works by defining a project as a sequence of activities (stages or phases) that you can plan ...


1

For the weaknesses there's a specific pattern that can be used My greatest weakness would have to be my constant drive to strive for perfection, realistically there is no such thing as perfection so it's important to feel confident in a project being complete. However by acknowledging this and learning to overcome this it has lead me to produce some of my ...


1

A lot of strengths answers can be tailored to the organisation doing the interview. For example, with a company that prides itself on the knowledge of its staff then it might be worth talking about one of your strengths as your background reading and quick understanding of problem domains. For weaknesses I recommend answers that can be interpreted both as ...


3

TL;DR You can look at data and use inductive reasoning to formulate a hypothesis, or use deductive reasoning to define your product goals. Note that you must have a hypothesis or goal to test and measure; otherwise, you're performing the equivalent of asking random sea turtles which shoes to make for the world's fastest Olympic runner. Even then, you're ...


Top 50 recent answers are included