Few Project Management Tips

1,136 views

Published on

Few Project Management Tips

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,136
On SlideShare
0
From Embeds
0
Number of Embeds
188
Actions
Shares
0
Downloads
8
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Few Project Management Tips

  1. 1. Brief About Effective Project Management ( IT Industry) Ketan Raval www.letsnurture.com | www.letsnurture.co.uk
  2. 2. Page Titles / Screen Titles No Matter at which state you are, Never have “Untitled Page” in your project. Put Appropriate Page Title right at the beginning of the development www.letsnurture.com | www.letsnurture.co.uk
  3. 3. Form Validation Never Assume that your development is finished before testing. Form Validation must be done at developer end before passing to QA. www.letsnurture.com | www.letsnurture.co.uk
  4. 4. Favicon • If you are serving for CMS website or for any end client always put favicon. • Putting Favicon without asking will put good impression on your client. www.letsnurture.com | www.letsnurture.co.uk
  5. 5. Custom Login Dashboard • If you are using open source framework like wordpress joomla magento always cusotmize login page with client logo and css. www.letsnurture.com | www.letsnurture.co.uk
  6. 6. Always Use Project Name Correct • Always Use Project Name correct. Your client is very much attached to the name ( does not matter if you are not). • Never misspell or never put any other name in any document or server. www.letsnurture.com | www.letsnurture.co.uk
  7. 7. Browser & Resolution Testing • Browser & Resolution testing is not QA process. Yes QA will find more bugs but it is developer’s duty to develop uniform project and it must work smoothly in all resolutions & Browsers. www.letsnurture.com | www.letsnurture.co.uk
  8. 8. Manual For CMS • Kindly Provide Manual to Client at the end of the work . Most of clients are not techie so they need some kind of support document for all work. www.letsnurture.com | www.letsnurture.co.uk
  9. 9. Do Not Assume Never assume about scope of requirement. Always ask your client or business analyst about the scope of requirement www.letsnurture.com | www.letsnurture.co.uk
  10. 10. No Chat : keep it in Email Developer usually are not much interested in drafting email. But always draft an email and keep your immediate supervisor & BA in CC. In this way your entire team can be in on same page for the same project. www.letsnurture.com | www.letsnurture.co.uk
  11. 11. Thank you for reading till the end www.letsnurture.com | www.letsnurture.co.uk

×