How should I define time for an Aha! feature?

Has anyone used Conjoint Analysis for requirements management or prioritization? Please share your experience

How do you keep track of software requirements?

How do you know whether a User Story is well written or not?

During which milestones do you write or revisit epics?

How do you sync functional specs with design across multiple platforms?

What is the best way to keep track of software requirements with minimal effort?

What are the key constraints in determining API speed?

What tips do you have for dealing with scope creep?

Does anyone have a requirement gathering template?

What is a product sample report (with respect to an IT industry)?

Do you use UML (Unified Modeling Language) in your organization?

What are some resources for writing great user stories?

Should original feature estimates be updated regularly?

How detailed should your requirements be?

Do you group features by whether it is a base feature vs. a special-add on?

What's the best method for tracking and reporting on requirements and dependencies across scrum teams in other business units?

What is the best user story template for product managers?

How far in advance should you write user stories for?

What process do you use to prioritize product features required from multiple stakeholders?

How do you best manage unplanned feature requests from important stakeholders?

When you are developing mobile apps, do you write separate stories for UX and Dev (in your product backlog)?

What is the best way to document Business Logic and how do you keep track of the changes?

What is the best user acceptance template for final testing?