Which are hardware projects management guidelines in your organization
As anything, the answer really depends on what the project is and in which environment you're developing. The process will be different if it's a senior project or a commercial board bring-up, for example. Since you have not given details about your particular environment, here are some general unordered guidelines I can think of that may help:


Write down a plan and show it to anyone who would look at it -- take note of their advice and adopt what seems logical to you. There's definitely room for personal preference here.
Create milestones for the project and estimate how long they will take to achieve.
Decide on a time multiplier (this ranges from x2 to x5 and depends on your experience) and apply it to your timing predictions. This will give you a buffer, and ultimately be more realistic -- most people grossly underestimate the time and effort it takes to accomplish something, and many things are out of your control.  
Document all the problems you've encountered, and how you solved them. This will help you in the future, and in writing a report if you're required to.
Getting supplies takes time, and sometimes stocks run out just as you want to place an order. When you design a component into your system, make sure you can source it reliably!


I hope this helps a little bit, and good luck.