Prakash 的个人资料Prakash's - Online Repos...照片日志列表 工具 帮助

日志


The Effective Software Developer’s Book List

Good one. Books list classified as Introductory, Intermediate and Professional.
 
Blogmarking it
4月16日

Viewpoints on Pre Sales, Sales support at Software Service Firms

Very good article on Pre Sales. It answered most of the questions i had about Pre Sales. Must Read...

What is Pre Sales?

Pre Sales includes the entire gamut of activities involved in preparing to engage with prospects, clients and others and includes specific responses to client requests. Clients or companies that need software services and project implementations generally call for proposals or expect responses from their vendors and service providers. Although it is hard to generalize on the nature of or the contents of such proposals, most documents follow a structured framework: detailing the project, asking vendors for suggestions or solutions or proposals along with cost estimates regarding the work to be done. Typical Pre-sales support activities include:

  • Responding to client requests: Responses to clients could include informal responses, pointers to publications, colleterals or other references or take more specific forms like responses to proposals including: Request for Proposal (RFPs), Request for Information (RFI) and specific Statement of Work (SoW) or Work Orders
  • Supporting client visits: In some cases, clients or prospective clients may make a trip to offshore vendor's offices for a personal visit prior to engaging with them. This could include offshore client visits targeted at offshoring
  • Visiting clients and/or making presentations: Engaging clients for larger, complex deals involves a number of activities, including making presentations, meeting with clients to discuss specific aspects of their (client's) initiatives, to get a better understanding of the context in order to make specific recommendations in proposals. This may also include preparing proof-of-concept demonstrations and solution mockups.
  • Competitor Analysis and market scanning: This is a crucial aspect of pre-sales since many clients evaluate responses from multiple vendors, and responses should address such competitive scan. The analysis could include using online tools, subscribing and analyzing research reports, analyst studies, market research data etc.
  • Sales Support: Such activities may include supporting sales and account teams in responding to general client queries about solutions and capabilities. This could include partnering with onsite/client facing Sales or Business Development Managers to identify and convert prospects into customers.
  • Interfacing with other internal groups (within the organization) while responding to client requests. This is especially true of larger software service firms where Pre-sales people from one group/division may have to rope in Subject Matter Experts from other groups while responding to a client request or proposal
  • Marketing support: Large service firms work hard at differentiating themselves from others by formulating marketing messages and evolving Go-to-market solutions or customized offerings. This may also take a form of alliances with other software product development firms or niche vendors. Pre-sales activities may include leveraging such alliances to showcase extended capabilities to clients.

Blogmarking it for Future Reference: http://www.offshoringmanagement.com/PreSales.htm

Pre-sales support is a necessary evil: http://www.garamchai.com/mohan/ITP13Sep04.htm

 
4月15日

Creating The Culture For An Agile Environment

An Interestring from the book "Becoming Agile".

Migrating to Agile is more than changing your process. It also requires a change in culture. For most companies changing culture is the most difficult part. I believe this is true for several reasons. Here are a few:

  • Whether successful or not, companies get comfortable with their processes.
  • Many people still believe requirements change because they are poorly managed. They cannot comprehend a process that embraces change.
  • Most managers have been trained to control events. Empowering the development team to deliver and own the project is not intuitive or logical.
  • Job protection. In larger companies whole groups are dedicated to regulating and overseeing projects. An Agile team has less need for these services.

Via: http://www.infoq.com/news/2008/04/smith-creating-agile-environment

Orignial URL: http://www.methodsandtools.com/archive/archive.php?id=70

 

4月11日

25 Ways to Distinguish Yourself

Interesting Presentation from Rajesh Setty - Author of "Life Beyond Code".
 
I have seen this presentation some time back in 2006. Infact, i have added the book "Life Beyond Code" in my reading list only after seeing this presentation. For some reason i remembered to refer this presentation after a long time.
 
4月4日

Caring for the Team

Interesting Post.

The article, What Every Baby Needs to Thrive, highlights eight steps every baby needs to thrive. For example, the first one is, "Show your love." What I have done is take this step and draw similarities to how this would apply to the success of a development team. This exercise can transcend outside of development teams to other teams, but this is a blog focused on engineering.
I have not altered the steps provided in the article. Each step and how they can be applied to a development team can be seen below.
Step 1. Show your love
How to Apply: Acknowledge them, give them praise, constructive criticism, tone of voice, genuinely care for their progress, listen to them, coach them, help them help themselves.
Step 2. Care for your child’s basic needs
How to Apply: Give them the knowledge and tools necessary to be successful, provide training opportunities for them to take advantage. Rest them, don’t just sprint them month after month without a break. A well rested employee is more productive. Reward them when they have done well, instruct them when they have not. Show them what it means to be a good developer. Provide a welcoming team atmosphere, lead the culture promoting it, and provide frequent feedback.
Step 3. Talk to your child
How to Apply: Communicate openly and frequently, listed and hear them, ask them how they are, what they are doing, learn how to help them.
Step 4. Read to your child
How to Apply: Present to them, demonstrate and show them what you know, teach them skills that they will learn to admire and achieve so they may help themselves.
Step 5. Stimulate all his senses
How to Apply: Give them a broad range of experiences, don’t just stick them in one technology or one facet of a project. Teach them all the parts of the project. See where there interests and skills develop. Groom them for future development in several areas.
Step 6. Encourage new challenges
How to Apply: Encourage them to raise their bar higher, step out of their comfort zone, teach a class, present a session, develop leadership skills. Teach them to teach others. Train the trainer.
Step 7. Take care of yourself
How to Apply: Lead by example, if you are not well rested (on top of your game), it becomes difficult to instill this sense amongst the team. Continue your education to grow and lead. Find time for yourself away from the team.
Step 8. Find good childcare
How to Apply: Develop a good team atmosphere. Who do you want your developers to emulate? Find mentors, get them training, pay for good speakers, find the right conventions. Encourage them to care for each other, to present to each other, to respect one another.

Original URL: http://elegantcode.com/2008/04/02/caring-for-the-team/