Words: 3557
The term has become popular with business authors and journalists as shorthand for the trend of leveraging the mass collaboration enabled by Web 2. 0 technologies to achieve business goals. The difference between scrounging and ordinary outsourcing Is that a task or problem Is outsourced to an undefined public rather than a specific other body. In scrounging a client initiates the activity and the work may be undertaken on an individual, as well as a group, basis. Scrounging has potential to be a problem-solving mechanism for government and non-profit use.
Scrounging has its benefits, especially if the effort can be a collaborative one. With Decrescendo, though, scrounging becomes competitive, but the end result Is hat end-users usually find the best potential output from among very capable designers. We recently learned that Designators has so far attracted about 108,000 designers, and has doubled Its business In the past year. To further add value to the scrounging service, Designators has launched Broadsword, which is a premium logo marketplace for designs that did not win the competitions.
Interested clients can browse through these logos or designs. And designers can soul monotone those that are chosen. “Crowd-sourcing is a somewhat loaded term, particularly when it comes to impact ND public engagement”(Dunn, 2013)The Impact that scrounging has had on the field of interface design will focus on impact of a humanities crowd-sourcing activity. First of all, Not every research question or problem you encounter will be amenable to scrounging as a solution. The typology In our report seeks to set out a framework for understanding workflow work.
Second, the mistake large numbers reflex for high impact. Most of the valuable work we saw while writing the report Involved the self-selection of very small groups of people from the wider public. And their sustained intellectual engagement with the project. The thousands of volunteers which early crowd-sourcing projects point to do not represent a good point of comparison for the humanities. Valuable public impact can happen In small areas. It would be wonderful if we could convince founders and promotion committees of this truth. Finally, putting a mechanism in place for your contributors.
We will get the better result If talking to each other. Having a user forum to support discussions and mutual problem solving is essential. This will allow a non-institutional community to form around your project, it will help sustain it beyond the end of your ending, and It will give your project’s discussions far more exposure to uptake on social media. As more and more designers start turning to scrounging project to seek designers via scrounging websites, any graphic designer has to sit back and consider this new form of employment.
More experienced designers might view scrounging with skepticism while young, newly emerging designers see it as the perfect opportunity to try out their newly developed skills. First of all, I would like to talk about equal playing field. While scrounging may not place you entirely in an equal playing field with all your contemporaries, it does even out the scores of experience a little bit. Scrounging allows the total newcomer to the world of graphic design as good a chance of winning a design competition as a seasoned graphic designer.
Unlike many Job markets where years of experience are needed before you can find a decent Job, scrounging lets anyone try their hand at design competitions, whether experienced or not. In addition, everyone can choose his or her own hour to work. Since most scrounging Jobs are freelance/work at home projects, you really get to choose your own working hours, instead of sticking to a jugular am-pm work schedule. While an organized, structured self-implemented schedule is always probably a good idea for actually getting projects accomplished, scrounging lets you work however late into the evening as you Jolly well please.
This is perfect for designers who find that their greatest moments of inspiration hit them long after normal office hours have expired for the night. Finally, it is very flexible of commitment. Scrounging is a great way to stay busy and employed during those months because it allows designers to choose their own periods of commitment to projects. When many industries are not hiring summer employees because they do not consider their short time commitment as worth the training investment, scrounging competitions are wonderfully flexible for start/end dates.
Moreover, the challenging of incorporating scrounging in design project should be concern. First of all, I would like to talk about Images. As a small business owner you need images for your Web site, you need them for printed materials, you need them for blob posts, and you need them for a million other reasons. For example, you probably do not have the budget to hire a photographer or graphic signer to create the perfect image for you. So, scrounging the task and use Creative Commons licensed Flicks photos.
There are quite literally millions of photos to choose from courtesy of the kind strangers who upload quality images to application. You may never have to pay for another image again. Moreover, in terms of usability testing, While I would not necessarily trust complete usability testing of your new mobile application to a bunch of strangers, scrounging usability while you are still early in the project or if you know what you are looking for can provide a tot of insight. Scrounging online usability testing should be used as a complement to an already established test cycle, and is not a replacement.
And to help you do that, there are some applications that will allow you to do survey-based and full-service usability testing on Web & desktop applications. Finally, the challenges in the office should be focus because the environment in the office is the primary concern. I would like to talk about the competition. You may have a crowd, but all of them are competing against each other for the winning idea versus working gather to come up with something bigger than any of them could on their own.
Plus, you must wade through thousands of “ideas” in order to find one great one. Than to employees or contractors”(Scenically, 2012) I would like to focus on the propose of a solution for generating interest in your design project from an online community. As our understanding of participatory cultures advances, there is a growing interest among practitioners and scholars in how best to take charge of the creative, productive capabilities of Internet users for specific purposes.
A number of inline businesses in the past decade have actively recruited individuals in online communities to design products and solve problems for them, often motivating an online community’s creative output or harnessing their creative input through the format of an open challenge with various rewards. Organizations that issue specific tasks to online communities in an open call format engage in the practice of “scrounging. ” Scrounging is a model for problem solving, not merely a model for doing business.
The scrounging model is also well suited to organizations’ marketing and public relations goals, as the process of managing an inline community allows organizations to forge close relationships with publics and allows consumers to participate in the making of brands, it is important to understand how scrounging works so that the collective intelligence of online communities can be leveraged in future participatory media applications for the public good.
I further define the scrounging model by putting forth a typology of scrounging. Ultimately, these types may inform the design of future participatory media applications for governments, non-profits, and activists hoping to solve pressing political, social, and environmental problems. Scrounging is necessarily dependent on the Internet. The speed, reach, anonymity, opportunity for asynchronous engagement, and ability to carry many forms of media content makes the Internet a crucial prerequisite for scrounging.
Certainly these processes can be taken offline with some success, but the platform of the Internet elevates the quality, amount, and pace of cooperation, coordination, and idea generation to a point that warrants its own classification. Cultures have always been participatory, long before the Internet, with roots in democratic process, collective decision-making, ND cooperation for survival. But participatory cultures on the Internet take on a new quality, a new scale, and new capabilities. Furthermore, all scrounging types rely on the notion of collective intelligence.
Conceived of collective intelligence as a form of universally distributed intelligence, constantly enhanced, coordinated in real time, and resulting in the effective manipulation of skills. The Internet is the technology capable of this degree of coordination of intellect, and thus as the capabilities of the Internet grow, so do the possibilities for leveraging this intellect. Given the will to act, robber solving with collective intelligence and networks can be scaled-up to address even global concerns.
Finally, all individuals engaged in a scrounging application, or any aspect of participatory culture, are in some way motivated to participate. This may seem obvious, but understanding how and why individuals participate in scrounging applications is necessary to design effective problem solving applications going forward. A number of interviews and surveys have been conducted at various scrounging sites, with each study asking individuals in those crowds to explain why they participate.
These studies indicate that there are many common reasons why people participate, both intrinsic and extrinsic, but there is no opportunity to develop one’s creative skills, build a portfolio for future employment, and challenge oneself to solve a difficult problem are motivators which emerge among several scrounging cases, but some crowds are driven by financial gain and do not mention these motivators. Drawing from these existing studies, some motivations for individuals in crowds that emerge across more than one case include. In terms of solution for evaluating the skill set and quality of the code submitted y potentially unknown users.
Test Driven Development: if there is one practice above all others which contributes to better code quality and fewer bugs it is ADD. On the plus side it can be used on any type of project, Agile, Waterfall or other. Its roots go back a long way but it was a forgotten practice until XP resurrected it. When run as part of a continuous integration cycle with frequent automated builds and tests the practice is Unit Testing on steroids. However it does not Just happen by mandating it so. Most developers do not know how to do it, they need training and help (coaching) to do it.
Even then it is going to be a learning experience, don’t expect it to become prevalent overnight. Acceptance Test Driven Development (ADD) is the next level up from unit test based ADD. Here those making the requests for development not only specify their acceptance criteria but do so before any development happens, and do so in a way that they can be automatically executed. In many cases professional Testers need to work with the “Customers” to create such testing. Continues Integration (C’): This is a valuable practice on its own – making sure code builds and new code doesn’t break anything that already exists.
When coupled with ADD and ADD to create automated, repeatable, test suites, it is an order of magnitude more valuable. Pair Programming: The controversy over pair programming seems to have died down, but then so too have examples of people actually doing it. A shame really, it is instant code review, it is two-heads better than one (think of commercial pilots or surgical teams). It also allows developers to focus intensely on the work in hand – few distractions from telephone calls, e-mails, SMS, and all the other rubbish that distracts us so easily. Code review: The next best thing to pair programming.
People will not pair then at least code review. Put in place a lightweight process that happens as soon after the code is written as possible. Static analysis tools: in the past static analysis tools have gotten a bad name for themselves. The current generation are a lot better and while they are not a true substitute for a code review. Coding standards: Traditionally I’m not a fan of coding standards. In my experience too many teams waste to much time debating and arguing over coding standards and when they are put in place they can be used as a tool for some developers to bully others.
However, if you can overcome those problems then they have a valuable contribution to make. Start by having a group discussion – face-to-face, not over e-mail or on a mailing list – about what could be in a coding standard. Find the areas of agreement and have three or four categories: a very few items as “mandatory’, more items as “recommended” and more as “candidates. ” These third groups are possible candidates for inclusion in recommended or mandatory but need some consideration. The fourth group for things you agree not to standardize on.
Then review these guidelines every three or o mandatory, and if some aren’t working then remove them or demote them. Then, don’t use coding standards as part of your review. Developers should follow them out of honor. But Just in case you miss one, automate them. Set your static analysis tools up to run your coding standards against code that is checked in. Remove the human from the loop and remove the bullying. Automate: In case it hasn’t sunk in yet, most of the suggestions so far can be automated, and should be automated. Not automating them means they take time to do and are therefore expensive in the long run.
Automation might cost in the short run but it makes things cheaper overall. Refinancing (refinancing tools): The whole point of refinancing is to improve the code quality and, more importantly, the overall design. If it is not then something is wrong. You can, and people do, refractors without automated unit tests but this is equivalent to a high-wire act without a safety net. With the safety net in place refinancing should be a frequent activity and one that does not take up lots of time. Show and Tell (early): maybe not immediately obvious why this one should lead to better code but it will.
By regularly showing potential customers of the software what they are getting developers need to keep their code near to release state. This forces more, smaller, steps in development. The second reason why this helps is that feedback comes more regularly. This provides positive guidance on what is going right and will point out when things are going in the wrong direction. Finally, if developers are scared to show their work in progress to users and customers then its time to run up the red flags and look for trouble. User Tests extends this reasoning. User tests provide another line of testing which helps detect problems early.
Similarly, working on smaller pieces/projects provides for more small steps. Before each step there is an opportunity for re-adjustment and course correction both at the work planning level and at the code level. Finally, Team cohesion is important because without it the team are running in different directions and doing different things with the code. Part of team cohesion must be a shared view on the development objectives, the design ideas in the code and what makes for good code. Developing a project timeline by scrounging is a cornerstone of any project management strategy.
But s many IT projects managers have learned, developing and adhering to a timeline is not easy. From technical glitches to human resource problems, unexpected complications can pop up at any time, quickly throwing an IT project off-track. “Project Timeline lets you answer questions about how much work is happening at the studio on a given date, where you not the most busy or free, and when your Projects start and end. “(Hidden,2012)Regardless, a project timeline is an important component of time management planning and a useful project management tool for keeping your client informed and your project on target.
A project timeline allows an IT project manager to: 1. Identify potential problems before they delay your project; 2. Give customers earlier notice of potential delays or scope changes – before you go over your estimate; 3. Provide immediate, on-demand status reports regarding which aspects of the project are complete, due or running behind; 4. Always know where you stand in regard to each project, and whether you’re coming out ahead or behind financially; 5. Bill your client as project milestones are attained; and Track the actual time spent on all aspects of the project, so you can better 6. Plop developing accurate timeliness may be tough. After all, what IT project manager has not committed to a specific timeshare for a consulting project, only to encounter obstacles that set the project back. Even if it feels like you are guessing at how the project will go, a timeline is still a useful tool for time management planning and keeping your client informed. Creating one demonstrates that you are committed to achieving specific project milestones and to tracking progress toward them. First, talk to your client about the major project milestones that need to be achieved over the ours of the project.
Those milestones can become the building blocks of your project timeline. Fill in the space between them with the sequential steps that must be performed to move from one milestone to the next. When estimating the time required to accomplish each task, consider which team members must be involved, as well as the amount of time each individual can commit to the project. If your client is to be responsible for any aspect of the project, clearly define those tasks and set deadlines for accomplishing them.
Involve the responsible team members in defining hose deadlines, and ask for their commitment. The more you track your progress against timeliness, the easier it will be to develop them for future projects. Each timeline represents historical project management data you can later use to estimate the actual time needed for similar IT projects in the future. In terms of realistic, some IT project managers prefer to set internal target deadlines that are more optimistic than the dates you commit to in the timeline you give to your client.
This project management method is a good way to offset any unexpected delays that may arise. Another project management technique is to build in a little extra time to deal with any possible wrong assumptions, estimation mistakes, risks and scope creep. Even if the delivery dates you commit to are farther in the future than your client would prefer, keeping your project timeline realistic helps you fulfill your commitments and shows your clients they can trust you to be honest about what it will take to get the job done.
In terms of improvement when necessary, sometimes, due to circumstances beyond your control, a timeline must change. It often happens when he requirements for an IT project turn out to be technically impossible or exceedingly difficult, when customers change their minds in the middle of a project, or when the initial project requirements turn out to be Just a small part of a larger issue that must be resolved. In cases such as these, scrounging must adjust their expectations and commitments.
As the IT project manager, that means adjusting your timeline, and being sure to advise all participants of the changes immediately. For helpful project management tools to evaluate and address potential IT project scope hangs. By carefully drafting and tracking progress against a project timeline as part of your overall IT project management strategies, you will be more likely to keep your IT project on-time and on-budget. Your customers will respect the fact that you can keep them informed, even when a project falls behind schedule.
And that means they will be more likely to value the services you provide and recommend you to their peers. “Most brands that courseware are mostly inexperienced in a particular aspect so, moving forward, brands should take a more consultative approach to redounding or risk running into ethical issues with their audiences”(Peahen, 2013)As scrounging gains traction, risks also will emerge from companies that rightful owner of the resulting intellectual property.
Economic and ethical problems in scrounging are related to the type of scrounging services, the nature of the task and of the workers’ activity, as well as to the place where this activity is located. An overview of the economic model of scrounging services will be presented, together with a summary of the situation regarding labor laws. Based on this analysis, some possible solutions may be envisioned for speech science, and more generally language sciences, in order to deal with scrounging services in a more ethical and efficient way.