LinkedIn and How to go About Management of Social Media Profiles

Global Membership_August 5 2014

Figure 1. Global Membership_August 5 2014 from LinkedIn

Updates of that quaint Italian restaurant, some friends have just started talking about to the cultural revolution in Egypt and even branding one’s self for prospective jobs. Increasingly the idea of branding one’s self online is becoming the standard way of what some people “call job hunting”. One way I brand myself is to be apart of a website like LinkedIn. One reason to use a site like LinkedIn is the popularity of such sites (I.e. figure 1). LinkedIn has a massive amount of accounts from all over the world, giving someone like me a world stage to broadcast the business of me from. With broad casting to suck a large amount of people, it is important not to send out messages that are meaning less, other wise someone’s messages will get lost out in the sea of people inhabiting places like LinkedIn. I like these simple rules on how to talk on social media from “The B2B marketer’s essential guide” from Coast Digital (Bond, p. 9).

  1. Don’t treat social media as a broadcast medium – you can’t strike up conversations if you’re shouting.
  2. Don’t expect instant returns – it takes time to build relationships online too.
  3. Analyze the mutual benefits in all your offline relationships – it’ll help you use social media to create similar benefits online.
  4. Talk to the right people – are you building relationships with people who can help your long-term business goals?
  5. Map out your landscape – who do you know? Where do they hang out online? Who are your advocates? Are your competitor already in this space?
Figure 2. by Wesley Eversole

Figure 2. A Facebook group by Wesley Eversole

The first premise made by Coast Digital I interpret at make social media in to an advertising platform for yourself. This can help stop the shouting in to the void of a social network that some people tend to use social media for. The second statement can go for anything in life, I would not expect job offers to be popping up seconds after I update my LinkedIn profile, but if keep my profile reflecting my skills / career plan, then it will help me obtain a career. In the third statement the idea for it that I apply to LinkedIn is that if like a group of people with common interests find a group in LinkedIn that one can contribute to conversationally. The fourth statement I feel is just more of the same from the third statement, have connections to people who will add to one’s worth in the eyes of an employer. The last statement is the most if applied to structuring connections on LinkedIn. An example of what social networks look like is figure 2, this web is a web graph of a group I belong to on Facebook. One can see all the connections or lack of connections to each node (one node is one person). For example if everyone in the web graph was attempting to get hired by the largest node, the largest node would have most contact with people directly connected with them. If the largest node hires one of its direct connections it might look in to who is connected to that person. Now on the other side of this hypothetical hiring event, knowing who is connected to the person hireling may help a person find out what skills the employer might be looking for in its prospective employees. The way skill information is shared in LinkedIn is by a tagging system. A paper Yi-Ching Huang, Chia-Chuan Hung and Jane Yung-jen Hsu titled “You Are What You Tag” bring up the how much a person can learn from how people tag internet bookmarks. They mentioned that a tag can have different meaning to different people (p.2). In the realm of skill tags in LinkedIn I would suggest staying with tags that one can prove that they do have the noted skills.

Following these suggested rules may not be the sole reason any one will be hired from LinkedIn but it can help make someone’s interaction with professionals stand out. When it comes to a job market being identifiable will go along far in helping any job hunt.

References

Bond, D. (n.d.). Demystifying social media (p. 27). Coast Digital.

LinkedIn (2014) LinkedIn Global Membership August 5, 2014 Retrieved October 28, 2014 from

http://press.linkedin.com/ImageLibrary/detail.aspx?MediaDetailsID=544

Huang, Y., Hung, C., & Yung-jen Hsu, J. (2008). You Are What You Tag. 1-6. Retrieved October 18, 2014, from http://www.aaai.org/Papers/Symposia/Spring/2008/SS-08-06/SS08-06-008.pdf?origin=publication_detail

Advertisements

Agile tasks lists, what does “done” mean in Agile?

In the world of development having a plan is important to help focus ideas. Having a plan can help direct work flows and generally make project with a lot of people easier to organize. If the plan is too rigid, that once a part of the project is finished that part is ready to ship it can hinder the projects work flow. In development ecosystems like agile plans or task list help guide teams towards a finished product. At the end of each sprint there is a retrospective, which in the team will put down a completed or “done” task. Tasks marked as “done” maybe finished but are not exempt from change.

What is Scrum? by Henrik Kniberg

What is Scrum? by Henrik Kniberg

The image from Henrik Kniberg slide show about agile development I think embodies the main idea of what an agile task list should be. It’s simple enough that it can change, without being to simple that nothing can be gained from it. It is also not so structured that nothing can ever change in it. The book “Agile for Dummies” by Scott W. Ambler and Matthew Holitza looks at the what agile developers can gain by implementing a task list. The authors look at things like “Tracking Velocity”, which follows the “Done Tasks” or the deliverable work. Handling Deliverable work allows a team to deal with small part of the over all projects and allows a set task to have a well-defined goal without having a strict overbearing plan like in waterfall(pp. 20-24). Since fluid nature of agile tasks allows the task to change throughout development, there has been research into this aspect of agile. The paper “Requirement Gathering and Tracking Process for Distributed Agile based Development” by Rehan Akbar, Muhammad Haris and Majid Naeem, explored the ideas of agile’s ability to allow changeable tasks design in large agile development groups, when agile uses simple documentation. The papers finding on the agile development documentation, was that simple design allowed teams to quickly shift design goals. The shifting in-goal allowed the management team, they were following, to better direct the other teams to finish the project(pp. 432-434). The shifting in the agile can be the reassessment of task that a team thought was “done”. Moving a task from “done” to working goes back to Knibergs image, letting us know that having something be strict like a “done” task be able to become a “to-do” task breaks from development methods like waterfall. There is also a downside to the reevaluation of “done” tasks that everyone should know about. Moving task from a “done” state to a “being worked” on state can make a project drag on which no teams wants. A team when deciding on bring back a done task might want to thing about the current task list and re plan when to rework a “done” task.

References

Akbar, R., Haris, M., & Naeem, M. (2008). Requirement Gathering and Tracking Process for Distributed Agile based Development. 8th WSEAS International Conference on APPLIED INFORMATICS AND COMMUNICATIONS, 429-436. Retrieved October 12, 2014, from http://www.wseas.us/e-library/conferences/2008/rhodes/aic/aic69.pdf

Ambler, S., & Holitza, M. (2012). Choosing an Agile Approach. In Agile for Dummies (IBM ed., p. 74). Hoboken: John Wiley & Sons.

Kniberg, H. (2014) What is Scrum? [Diagram] Retrieved October 12, 2014 from http://blog.crisp.se/2014/10/08/henrikkniberg/what-is-scrum