Wednesday, 2 October 2013

Security Flaw at Tradus.com

Your personal information is at risk when shopping at Tradus.com website.

After a routine visit to Tradus.com, I thought of recharging my mobile from my iPad with the promo code "MOTAB1". After selecting the provider, I authenticated using my Facebook account to recharge my mobile. Soon after clicking "Proceed" button on shopping cart (Step 1) I see some others contact details (i.e. Shipping and Billing addresses) instead of my (logged in) address (i.e., on Step 2).

I think this is a major security flaw at Tradus shopping site. This way there is a potential risk at customer's personal information. Tradus is loosing its credibility.

Try this at home ... If you don't believe me.

Screenshot:



Mothukuru Sreenivas
www.msreeni.com

*******************************************************************************

Tradus Privacy Policy

*******************************************************************************
At tradus.com, we believe strongly in protecting the privacy of your personal information, and in using it only in ways that have been notified to you. This Privacy Policy is a legal document which principally sets out what personal information we collect and retain, how we use it, whom we may disclose it to, the security measures we take to protect that information, and how you can correct inaccuracies in the personal information we hold. You should read it in conjunction with the tradus.com Terms and Conditions.

If you have questions or concerns regarding this statement, you should contact tradus.com's customer service

The full policy is displayed below :

ibibo respects your privacy and recognizes the need to protect the personally identifiable information (any information by which you can be identified, such as name, address, and telephone number) you share with us. We would like to assure you that we follow appropriate standards when it comes to protecting your privacy on our web sites.

In general, you can visit the Website without telling us who you are or revealing any personal information about yourself. [We track the Internet address of the domains from which people visit us and analyze this data for trends and statistics, but the individual user remains anonymous.]

Some of our web pages use "cookies" so that we can better serve you with customized information when you return to our site. Cookies are identifiers which a web site can send to your browser to keep on your computer to facilitate your next visit to our site. You can set your browser to notify you when you are sent a cookie, giving you the option to decide whether or not to accept it. The information we collect and analyze is used to improve our service to you.

There are times when we may collect personal information from you such as name, physical address or telephone number. It is our intent to inform you before we do that and to tell you what we intend to do with

.............................................
..........................................
...............................
.......................
.............
........
....

© 2013 Tradus.com. All rights reserved. Policy - Contact Us
*******************************************************************************

Tuesday, 23 July 2013

What Makes You The Best Manager?

Are you mentoring or leading or managing a team for a while?

If not, you have time to revisit this article later in future. Until then, go over below links:
               Sri Chanakya Niti Shastra Chapter 1

If yes, you are on the right page. As an individual contributor you might have done miracles in project or team. But, your past (experience and contributions) alone doesn't help you if you want to reach the next level in your profession. What got you here won’t get you there. Now, go over below points carefully and see which better explains your leadership style as a manager.

Characteristics of Best Manager: 
  1. Sets a good example.
  2. Explains the reasons for instructions & procedures.
  3. Helps team members polish their thoughts before they present them to others.
  4. Is objective about things.
  5. Lets team members make own decisions.
  6. Cares about team members & how they are doing.
  7. Does not seek the limelight.
  8. Won't let team members give up.
  9. Gives personal guidance & direction, especially when team members learn something new.
  10. Is empathetic & understanding.
  11. Is firm but fair.
  12. Keeps a results orientation.
  13. Makes team members work out most of their own problems or tough situations.
  14. Lets team members know where they stand.
  15. Listens exceptionally well.
  16. Doesn't put words in team members mouth.
  17. Is easy to talk with.
  18. Keeps the promises s/he makes.
  19. Keeps team members focused on the goals ahead.
  20. Works as hard or harder than anyone else.
  21. Is humble.
  22. Is proud of those managers s/he has developed.
  23. Gives credit where credit is due.
  24. Never says "I told you so.".
  25. Corrects team members performance in private.
  26. Never flaunts authority.
  27. Is always straight-forward.
  28. Gives at least a second chance.
  29. Maintains an open door policy.
  30. Uses language that is easy to understand.
  31. Inspires loyalty.
  32. Really wants to hear team members ideas & acts on them.
  33. Lets team members set their own deadlines.
  34. Celebrates successes.
  35. Is open & honest.
  36. Doesn't hide bad news.
  37. Gives team members enough time to prepare for discussion.
  38. Is enthusiastic.
  39. Follows through.
  40. Is patient.
  41. Wants team members to "stretch" their skills.
  42. Gives team members his/her full attention during discussions & won't be distracted.
  43. Has a sense of humor.
  44. Handles disagreements privately.
  45. Reassures team members.
  46. Makes team members feel confident.
  47. Tells team members the "whole story.".
  48. Says "we" instead of "I".
  49. Makes hard work worth it.
  50. Can communicate annoyance without running wild.
  51. Is courageous.
  52. Insists on training.
  53. Is a stabilizing influence in a crisis.
  54. Gets everyone involved.
  55. Wants team members to be successful.
  56. Is optimistic.
  57. Operates well under pressure or in a rapidly changing environment.
  58. Has a reputation for competence with his/her own peers.
  59. Has a good understanding of the job.
  60. Is tough & tender.
  61. Believes we can do it, Sets attainable milestones.
  62. Communicates philosophy & values.
  63. Is perceptive; doesn't believe that everything needs to be spelled out.
  64. Has a strong sense of urgency.
  65. Preserves the individuality of his/her team members.
  66. Thinks & operates at a level above that expected.
  67. Wants to make the organization the best in the industry.
  68. Is willing to act on intuition; believes feelings are facts.
  69. Empowers team members.
  70. Is there when we need her/him.
  71. Enjoys his/her job.
  72. Likes to spend time with team members.

If Else Condition

if (you are a student)
  {
//  Check: 

               Books Online
               Is It Attitude Or Qualification That Matters

  }
else if (you are searching for a job)
  {

//  Check: 
               Competency Based Interview Questions
               Prototype Future Of Job Hunt
  }
else if (you are a fresher in company)
  {

//  Check: 
               Email Etiquette
  }
else if (you are leading or managing a team)
  {

//  Check: 
               Secrets Of Positive Feedback
               Guide To Get Things Done
               Time Management Matrix
               Different Types Of Leadership
  }
else if (you want to show some difference globally)
  {

//  Check: 
               54 Point Personal Branding Checklist
               Nine Things Successful People Do
               Secret Behind Being Extraordinary
  }
else
  {

//  Check: 
               Sri Chanakya Niti Shastra Chapter 1
  }

Wednesday, 12 June 2013

Would you like to look good or bad?

Are you good or bad? It doesn't matter if you live in isolation! Well .... if you are a social animal it depends on the way you project yourself before others.

I've seen many people who are good by heart & nature but they doesn't like to exhibit the same through actions. They seem to be more comfortable being the way they act/react rather than the way they are supposed to be. This result in people around them misunderstand for their wrong actions.

Let's assume person's appearance as a cake and his/her nature as cake's flavor or taste (i.e. Chocolate, Strawberry, Vanilla, etc.). Below are some pictures which shows a few variants of cakes. All cakes taste good, there is no doubt about it. Now, answer below questions.

1) Which cake do you prefer to be?
2) Which cake do you prefer to eat?

For both questions, 99.99% will opt for 'first' or 'second' or .... till 'sixth'. But, none prefer 'seventh' cake. Check out ...... why?

First

Second

Third

Fourth

Fifth

Sixth

Seventh


Your actions make you either look good or bad ... Before you react to any situation think about 'seventh' image ...  Think ... Think ... Think ...

Hope you got the answer!
Choice is yours


"Do all the good you can. By all the means you can. In all the ways you can. In all the places you can. At all the times you can. To all the people you can. As long as ever you can"



-Sreenivas Mothukuru

Sunday, 28 April 2013

Sprint Checklist

Article written by Sreenivas Mothukuru

After working for many years on projects developed using Agile (Scrum) I came up with below sprint checklist (3 week sprint). Please go over below items and help me fine tune the checklist. Thank you!



Before Sprint Starts
1
Book conference room for backlog grooming meeting
2
Review prioritized user stories in product backlog before attending backlog grooming meeting
3
Attend backlog grooming meeting
4
Book conference room for sprint planning meeting

Day 1
5
Review user stories in sprint backlog before planning meeting
6
Come up with Dev tasks for (already groomed) user stories
7
Come up with QA tasks for (already groomed) user stories
8
To come up with QA and Dev estimates
9
Identify (module/code) dependencies
10
Attend sprint planning meeting
11
Come up with testing scope document

Day 2
12
Review the priority of user stories
13
Everybody must have clear understanding about stories committed, otherwise get clarifications from Product Owners
14
Make sure all user stories have tracking bugs/tickets
15
Finalize testing scope document
16
Create and upload (unit) test cases
17
Arrange test case review meeting

Day 3 to 12
18
Update relevant information (i.e "Post Resources", modules touched, dependencies, CM/DBA tickets, Change Requests, etc.)
19
Verify the correctness of builds deployed onto QA environments
20
Work with CM team to resolve environment specific issues (if any)
21
Update test case document as per the feedback/suggestions received
22
Check Definition of done, details about WHAT and WHEN user stories will be DEV and QA complete, testing notes, etc.
23
Check whether roll-back plan is identified for all user stories?
24
Identify user stories which need Demos
25
Update QC/Rally/etc. with QA / Dev status
26
Test code changes on Dev boxes before pushing the changes to QA environment
27
Deploy code to QA after development and initial testing on DEV boxes is complete
28
Do Dovetails after every release
29
Update release wiki with dovetail information
30
Make sure all DB changes are committed to SVN with corresponding tracking ID
31
Create/Modify Hudson jobs every time the branch name changes
32
Run automation scripts in QA and Stage environments regularly
33
Coordinate with other dev teams (about release work distribution)
34
Coordinate with other QA teams (about release work distribution)
35
Communicate with Dev and Scrum master on sprint related issues (in any)
36
Ensure all user stories are in verified in QA environment
37
Ensure Performance testing is done for stories (if required) in QA
38
Ensure required hardware/software/applications/etc is set for Performance testing for stories (if required) in Stage
39
Complete Demos
40
Follow up with the user stories that needs to be verified and accepted by product Owners
41
Provide acceptance in QA environment
42
Send QA acceptance email communication to all scrum teams
43
Create release branches
43
Create release RPMs

Day 13 & 14
44
Ensure all user stories are verified in Stage environment
45
Ensure Performance testing in complete in Stage
46
Provide Stage team environment acceptance
47
Send stage acceptance email to all scrum teams

Day 15
48
Update Definition of done
49
Participate in the release
50
Verify user stories in Production
51
Provide Production environment acceptance
52
Send Production acceptance email to all scrum teams

Post Release Work
53
Follow up with the user stories which needs to be verified by Product Owners after release
54
Close all tracking tickets (bugs / user stories) which went to production
55
Arrange retrospective meeting, discuss with team and come up with retrospective notes
56
Share retrospective information with entire team

- Mothukuru Sreenivas