HN Explorer

vikashkoushik

↗ HN profile [ 73.4 ms ] full profile

No user record in our sample, but vikashkoushik has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.

  1. 1 points 0
  2. 1 points 0
  3. Framework to Analyze Customer Feedback (zepel.io)
    1 points 0
  4. Five ways to collect customer feedback (zepel.io)
    1 points 0
  5. Common Git Commands (zepel.io)
    1 points 0
  6. Git Commands Every Developer Should Know (zepel.io)
    1 points 0
  7. Git Workflows you can use to deliver better code (zepel.io)
    1 points 0
  8. Agile Sprint Planning (zepel.io)
    2 points 0
  9. Learnings on how to create a team structure for agile development (zepel.io)
    1 points 0
  10. Three product development problems your team is facing and how you can fix it (zepel.io)
    2 points 0
  11. Create a Robust Agile Team Structure: Learnings from Others' Mistakes (zepel.io)
    2 points 0
  12. Git workflows to improve your development workflow (zepel.io)
    4 points 0
  13. Problems hurting your product development (zepel.io)
    2 points 0
  14. Product development problems you didn't know your team is facing (zepel.io)
    2 points 0
  15. Four-step guide to make product improvements (zepel.io)
    2 points 0
  16. Git Workflows you can use to deliver better code (zepel.io)
    1 points 0
  17. Product Managers should remove uncertainty. Here's why (zepel.io)
    2 points 0
  18. Project management challenges nobody talks about (zepel.io)
    3 points 0
  19. Are issue tracking tools hurting your product development? (zepel.io)
    3 points 0
  20. Scrum artifacts and how to use them (zepel.io)
    1 points 0
  21. Stop disappointing customers. How to build better software features (zepel.io)
    2 points 0
  22. Five sprint retrospective ideas you can run even remotely (zepel.io)
    1 points 0
  23. Feature is a better abstraction than issues (zepel.io)
    2 points 0
  24. Definitive Guide to Agile Scrum Sprint (zepel.io)
    2 points 1
  25. Ask HN: What does an Epic represent for your team?

    From the conversations I've had, for most software teams, epic basically equals to a feature they are building. It's broken down to user stories and tasks. I'm curious to know if you use an Epic to represent something…

    5 points 5