Monday, September 30, 2019

Case assignment

In order to prevent this state from continuing, the office of chief financial officer believes that $1 00 million SAID WOUld cover the risk enervated by low level of cash and liquid securities and guarantee for the bank's financial stability. Types of Risks The main risk faced by NAB from the low cash level is liquidity risk, and there are two risks derived from liquidity risk: contagion risk and funding risk. Liquidity risk refers to an DAD will have insufficient funds to meet its financial obligations when due.In fact, a low liquidity ratio in one bank could affect the entire system, in other words, it can lead to contagion risk that the payment system collapses as a result of default by ADDIS in general. Hence manage equity adequately could minimize serious problems arise in the future (Jasmine et a', 2012, IPPP). While the funding risk refers to an DAD is difficult to maintain sufficient funds to cover its loans. It is closely related to liquidity risk since failure to rollover l iabilities will result in a liquidity crisis for the AD'.Causes of The Risks There are several causes of the liquidity risk. A liquidity risk could arise due to the mismatch in the maturity of the bank's sources and uses of funds. The maturity mismatch is an imbalance between the average maturity of a ban? Assets and its liabilities. Observed by Agate (2009), approximately half of the funds in banking system are provided by deposits, and the majority of them are in transaction or saving accounts that could be withdrawn immediately. Ender this unreasonable liability structure, when customers withdraw a great deal of deposits, a liquidity risk can be caused. 2. An economic factor can influence the liquidity risk within ADDIS (Somalis, 2010). For example, during a crisis, lenders are likely to panic and cause a run on their DAD to withdraw their funds. On the other hand, a boom in the economic yes could also cause a liquidity risk because of active demands for investment in various ind ustries such as real estate, mining, etc.Most funds of these investments are from bank loans, which bring a credit risk (I. E. Borrower defaulting). Once the bank suffer a loss of its assets, the liquidity ratio will decrease thus increase the liquidity risk. 3. Monetary policy could affect the liquidity risk in a bank as well. For example, if the interest rate is expected to decrease in the future, customers will deposit now in order to decrease the loss of wealth. Meanwhile, bank loans will crease because customers will borrow money in the future due to low expected interest rate.However, when the interest rate is expected to increase in the future, firms' demand for loan will blow up, and customers is unwilling to save money now due to expected high interest rate in the future, hence cause a liquidity shortage which give rise to liquidity risk. Solution NAB is facing a serious condition now where the liquidity ratio is low. It has to come up with several strategies to manage the liquidity risk that is likely to cause a bank to bankruptcy. 1.The office of CROP believe that about $100 million ADD would solve the robber, because by holding this amount of cash, exchange settlement funds and liquid assets, it is able to maintain the liquidity when unexpected shortages of liquidity occur. Another method to manage liquidity risk is to balance asset and liability of the bank by matching the maturities. In order to do so, the bank deposits should be allocated in well-organized maturities assets. Hence, the demand for liquidity from the matured deposits could be fulfilled from the liquidity of the matured assets (Greenberg and Thacker, 1 995, Pl 72).

Sunday, September 29, 2019

Accounting Education: an international journal Essay

ABSTRACT This study into the perceived importance of oral communication skills in accountancy included the collection and analysis of quantitative and qualitative data from a national survey of New Zealand accountants, followed by a series of semi-structured interviews. Survey and interview data reveal agreement with existing literature: New Zealand accountancy employers find all oral communication skills somewhat important and a number of specific skills extremely important, but employers also report seldom finding the required level of oral communication proficiency in new university graduates. The study produced an inventory of 27 individual oral communication skills that will be useful to similar investigations in different national contexts. Additionally, the findings of this study may be useful to curricular development both in the New Zealand and international contexts. See more: Satirical essay about drugs KEY WORDS: Oral communication, workplace communication, listening, presentation skills, telephone skills 1.Introduction Academics and practitioners do not always concur but, in the case of communication skills in accountancy graduates, these two sets of stakeholders are in firm agreement: both written and oral communication skills are extremely important in the accountancy work- place (Albin and Crockett, 1991; Albrecht and Sack, 2000; Borzi and Mills, 2001; Hock, 1994; Johnson and Johnson, 1995; LaFrancois, 1992; McDonald, 2007; Morgan, 1997). This agreement extends across international boundaries, as a number of studies around the globe have reported the high value placed on communication skills, for example in the UK (Morgan, 1997), USA (Smythe and Nikolai, 2002), and Australia (Tempone and Martin, 2003). In New Zealand, the site of the present study, academic studies into the importance of communication skills in accountancy and the challenges of teaching those skills (Gardner, Milne, Stringer and Whiting, 2005; McLaren, 1990) have multiple corollaries in the workforce. Accountancy job advertisements regularly request both oral and written communication skills; competency in oral communication is emphasised on the website of the New Zealand Institute of Chartered Accountants (NZICA); and oral communication is an explicit component of the assessment structure of the PCE2 examination, which concludes the second (and final) stage of training towards becoming a Chartered Accountant in New Zealand. However, both formal studies and anecdotal evidence suggest that new accountancy graduates often do not possess communication skills sufficient to meet the demands of the workplace, particularly in the area of oral communication (Adler and Milne, 1994; Courtis and Zaid, 2002; Gray, 2010; McLaren, 1990; Zaid and Abraham, 1994). Students in New Zealand may graduate with a university degree in accountancy after three years of full-time study. (Accountancy may also be studied in less rigorous programs at polytechnics and institutes of technology.) The intensity of the university programs of study, which are accredited by NZICA, means students have a challenging workload of technical study and very limited opportunity to take elective or ‘liberal’ courses. Of course, limited class time and the resultant curricular pressures and inadequate skill mastery are not unique to the New Zealand accountancy classroom (Pittenger, Miller and Mott, 2004; Wardrope and Bayless, 1999). The globally-recognised problem of insufficient oral communication skill in accoun- tancy graduates leads to a series of questions that need practical answers: . How should university educators respond, strategically and pedagogically, to this reported lack of oral communication skills in new graduates?. What approaches and assessments within university courses will best meet the needs of students aspiring to successful accountancy careers? . To what extent is the development of such skills in students the responsibility of the university and what is the role of the workplace in developing oral communication skills? Before university educators can make any meaningful decisions concerning pedagogy or curricula, and appropriately teach the oral communication skills needed for a successful accountancy career, they need concrete information regarding exactly which specific skills are most valued and most needed in accountancy. Thus a research question was formu- lated: to ascertain the value of specific oral communication skills in new graduates, as perceived by New Zealand accountancy employers. It was hoped that answers to this research question would provide educators with specific information with which to consider their optimal pedagogical responses. The research question led to the construction and implementation of this longitudinal study. Initial research objectives were: . To determine how much importance New Zealand accountancy employers place  on oral communication skills in the new graduates they hire. . To determine what specific kinds of oral communication skills are required by New Zealand accountancy employers in new graduates. . To determine the degree to which accountancy employers are finding the required oral communication skills in newly-graduated accountancy students. The study included the collection and analysis of quantitative and qualitative data, from a national survey of New Zealand accountants, followed by a series of semi-structured Oral Communication Skills in New Accountancy Graduates 277 interviews. Initial findings from the first-phase survey have been reported elsewhere (Gray, 2010). Overall, survey and interview data revealed that accountancy employers find all oral communication skills somewhat important and a number of specific skills extremely important, but that the required level of overall oral communication skill was seldom found in new graduates. Accountancy employers agreed that the possession of strong oral communication skills improves a graduate’s chance of succeeding in the hiring process and also of progressing in his or her career. The study produced an inven- tory of 27 individual oral communication skills, of which listening skills were most highly valued by accountancy employers, and formal presentation skills were considered least valuable, although there was disagreement on this point. It is hoped the oral communi- cation skill inventory will be useful to similar investigations in different national contexts. Additionally, the findings of this study may be of use both in the New Zealand and inter- national context in the long-term planning of curricular development. 2.Literature Review Studies of communication in accountancy agree broadly on the importance of written and oral communication skills. Many formal and informal studies to this point have tended to use general terms such as ‘communication skills,’ or the even vaguer term ‘generic skills’;1 it is difficult to ascertain the precise meaning of such all-encompassing terms as they apply to chartered accountancy. For example, Zaid and Abraham (1994) studied the problems encountered by accountancy graduates early in their employment careers, and reported a primary area of difficulty to be in ‘communication with others.’ Baker and McGregor (2000) compared the importance perceived in communication skills by a number of accountancy stakeholder groups; this study, too, only uses the broad term ‘communication skills.’ De Lange, Jackling, and Gut (2006) surveyed Australian accoun- tancy graduates and found that students reported themselves to have a significant skill deficiency in the specific areas of ‘interpersonal skills’ and ‘oral expression’; these two broad categories, however, were no more closely examined or defined. Within the smaller number of studies that have examined a particular set of communi- cation skills in accountancy, most have focussed on written communication skill (Albrecht and Sack, 2000; Ashbaugh, Johnstone and Warfield, 2002; English, Bonanno, Ihnatko, Webb and Jon; Ng, Lloyd, Kober and Robinson, 1999; Webb, English and Bonanno, 1995). Very few studies have examined oral communication specifically, or identified individual oral communication skills. Morgan (1997) is an exception: in a study of accountancy professionals in England and Waleses, 1999; Hall, 1998 he identifies 13 individual skill areas within oral communication activities in accountancy. There is no agreement on a classificatory inventory of such skills. One study into oral communi- cation, by Maes, Weldy and Icenogle (1997), surveyed American business employers from a broad array of industries on graduates’ possession of another 13 distinct oral communication skills. Maes et al. (1997) and McLaren (1990) both specifically list ‘listening’ as a desirable communication skill and, more recently, Goby and Lewis (2000) have examined listening as a specific business communication skill. Other research has variously investigated a number of individual oral communication skills across a range of business industries, including conveying expertise through spoken communication and giving intelligible explanations (Smythe and Nikolai, 2002), delivering formal presenta- tions (Wardrope, 2002), and participating in a range of more informal presentations (Crosling and Ward, 2002). The first phase of this study drew together the foci and findings of previous studies in relation to the  production of a comprehensive list of oral communi- cation skills (Gray, 2010). 278F. E. Gray and N. Murray Ascertaining the particular requirements of accountancy employers in regard to specific communication skills should be of assistance to university educators planning the curricu- lar content and assessments of university courses, as academics and practitioners agree that written and oral communication skills are two major areas needing more attention in the university accountancy curriculum (Albrecht and Sack, 2000; Henderson, 2001; Simons and Higgins, 1993). However, the relationship between workplace demand and classroom instruction is not necessarily simple. While a considerable body of scholarship has recommended a variety of curricular improvements for university level accounting education (see, for example, Henderson, 2001; Sin, Jones, and Petocz, 2007; and Usoff and Feldmann, 1998), the literature reflects a significant concern in relation to the transferability of taught communication skills from the university classroom environment to the ‘real-world’ environmen t of the accountancy workplace (Beaufort, 1999; Cooper, 1997; D’Aloisio, 2006; Davies and Birbili, 2000; Kemp and Seagraves, 1995; Thomas, 1995). A number of academics and employers suggest that universities should not bear the entire responsibility for developing ‘workplace-ready’ communication skills in students. They argue that organisations employing new graduates—and graduates themselves— should share the responsibility for developing contextualised and discourse-specific com- munication competencies (Ford, 2009; Hayes and Kuseski, 2001; Muir and Davis, 2004; Triebel and Gurdjian, 2009). Such competencies, after all, are developed by means of a number of contributing factors, including age and maturity, as well as familiarity with and length of exposure to a specific discourse community. University training, however comprehensive, cannot encompass all these variables. Research into accountancy education has also recognised the particular problems faced by English second language (ESL) speakers striving to develop written and oral communi- cation competency as well as the technical proficiencies required in accountancy work- places (Andrews, 2006; McGowan and Potter, 2008; Webb et al., 1995). Several studies in New Zealand and internationally report on the difficulties that ESL accountancy gradu- ates  face in a competitive hiring environment (Birrell, 2007; Jacobs, 2003; James and Otsuka, 2009; Kim, 2004). With regard to the specific question of developing communication skills within univer- sity-level accountancy instruction, scholars have suggested an array of learning and assessment approaches (Adler and Milne, 1997; Milne, 1999; Milne and McConnell, 2001; Tempone and Martin, 2003). This study recognises that developers of curricula must balance data regarding workplace demand with institutional and accreditation- related demands and a number of other pedagogical considerations. Notwithstanding, educational responses to the challenges of developing oral communication skills in students may be usefully informed by empirical data identifying the particular skills most highly valued and most pressingly needed within accountancy, as perceived by employers themselves. This study provides such data. 3.Method The project was conducted in two stages over the course of approximately six months. In phase one, a questionnaire was mailed to all New Zealand chartered accountancy firms, and this was followed in phase two by a series of telephone interviews with accountancy professionals. Prior to data collection, ethics approval was sought from and granted by the Ethics Committee of the authors’ institution. Questionnaire and interview respondents were provided with a written description of the project, were assured of confidentiality, and granted permission before their responses were recorded. Oral Communication Skills in New Accountancy Graduates 279 3.1Questionnaire In the first stage, a questionnaire was sent to all New Zealand chartered accountancy firms, containing a series of questions concerning the quality of oral communication skills pos- sessed by new accountancy graduates, the specific oral communication skills which employers desire, and the role of oral communication skills in the hiring process (Gray, 2010). The majority of the questions were designed to be answered on a five-point  Likert scale, but the questionnaire also included several short-answer questions. The questionnaire instrument was developed through a series of iterations. The findings and design of previous New Zealand and international research studies that had identified specific communication skills were consulted (including Gray, Emerson and MacKay, 2006; Maes et al., 1997; McLaren, 1990; Morgan, 1997; Smythe and Nikolai 2002), and the individual oral communication skills collated. The catalogue of individual skills was further extended through conversations with university colleagues in the communi- cation and accountancy departments, and then the input of New Zealand accounting prac- titioners was solicited from a pilot study. The aim of these iterations was to create the fullest possible inventory of oral communication skills, and to reflect the unique aspects of the New Zealand accountancy context. A foundational study was McLaren’s 1990 investigation into communication skill in New Zealand accountancy. One important construct borrowed from McLaren was the distinction between listening attentiveness and listening responsiveness. Constructs were also adapted from studies conducted by Morgan (1997), Zaid and Abraham (1994), and De Lange et al. (2006). Smythe and Nikolai’s oral communication concerns model (1996, 2002) proved particularly useful in the construction of this questionnaire. This model identifies three categories of concern as a framework for grouping oral com- munication skills: self-concern, task-concern, and impact (or outcome) concern. Smythe and Nikolai postulate that a progression takes place from one category of concern to the next in line with a person’s career progression and his/her growth in experience and confidence in communicating orally in the workplace. Since the target population for this study was a constituency at a mature career stage within chartered accountancy firms, Smythe and Nikolai’s ‘progressive’ divisions were not retained (although a number of their questions were incorporated, particularly in the areas of task concern and impact concern). Instead, divisions between questions were created in relation to different audiences, building on the finding of a related study (Gray et al., 2006) that New Zealand employers report new graduates to significantly lack audience awareness in their communications. After a comprehensive list of specific oral communication skills was generated, the questionnaire draft was piloted on four accountancy professionals, and their feedback enabled  questions to be refined. A number of skills that were initially individually ident- ified were modified and condensed into a smaller number of broader and more inclusive skills: for example, ‘Building audience confidence in recommendations’ and ‘Projecting an image of sincerity and commitment’ (both ‘impact concerns’ from Smythe and Nikolai’s taxonomy) were combined into the one, more inclusive skill category, ‘Convey- ing a knowledgeable and confident demeanour.’ Additionally, feedback from the pilot study led to the second of the two specified listening skills being more fully explicated, thus: ‘Listening responsiveness: (that is, acting appropriately on messages received).’ Again building on feedback from the pilot regarding usability, the questionnaire as a whole was divided into three sections. Section A captured introductory information including the size of the organisation and the qualifications held by new graduates hired in the last three years. Section B listed the full, final inventory of 27 individual oral 280F. E. Gray and N. Murray communication skills, collected into the following audience-related divisions: I. Listening skills; II. Collegial communication skills; III. Client communication skills; IV. Communi- cation skills with management; and V. General Audience Analysis Skills. Respondents were asked to rate the importance of each skill, as well as the frequency with which this skill is found in new accountancy graduates. At the end of Section B respondents were invited to add to the questionnaire any other oral communication skills that they con- sidered important for new accountancy graduates. Section C, Final Questions, asked respondents whether oral communication training was available in or through their organ- isation, whether oral communication training should be included in university accoun- tancy education programmes, and finally to estimate the hours per working week a new accountancy graduate would be engaged in communicating orally. At the close of the questionnaire, respondents were given the option to volunteer for a follow-up interview. 3.1.2 Respondents.The questionnaire was sent to all chartered accountancy firms listed on the New Zealand online business directory, and was addressed to the Practice Manager as the individual most likely to have  in-depth knowledge of the process of hiring new graduates. New Zealand’s professional accountancy body, the New Zealand Institute of Chartered Accountants (NZICA) reports that 40.7% of its members work in the private sector, while the second largest percentage, 27.5%, are employed in Chartered Accountancy practices (2008 annual report). Working on the assumption that CA prac- tices hire a percentage of new graduates proportionate to their sizeable percentage of NZICA members, CA practices were chosen as the focal population for this study as they represent (in contrast to the private sector) a readily identifiable and readily contact- able group of employers.2 While the New Zealand online business directory listed 1,111 chartered accountancy firms as of 1April 2008 , a number of listed organisations had ceased operations or were uncontactable, and the questionnaire was eventually mailed to 760 firms. Of 760 mailings, 146 questionnaires were returned, producing a response rate of 19.2%. While this response rate was higher than the 15% usable response rate reported by McLaren in her 1990 study of New Zealand accountancy professionals, it remains margin- ally lower than the typical response rate for postal-based questionnaires (20 – 40%, as given in Frankfort-Nachmias and Nachmias, 1996). Possible reasons for this relatively low response rate include the fact that time and funding did not permit follow-up mailings, and also the fact that the target population is frequently time-poor and frequently surveyed. While non-response bias is an unavoidable concern when the response rate is less than 100 per cent, a low response rate does not necessarily equate to a non-response bias (Gendall, 2000). A degree of representativeness was observable in the geographical spread of respondents, the positions held by respondents (see below), and the types of businesses responding, suggesting generalisation across a range of accountancy business types is viable. The questionnaire was mailed to separate groups of potential respondents in six post- ings, each approximately 10 days apart. The order in which responses were received generally mirrored the order in which postings were mailed: that is, the first group’s responses were received before the second group’s questionnaires began to be returned, and so on. As a record of receipt for each individual survey was not kept, early versus late response bias cannot be checked. As a single mail-out technique was used for each individual, it  may be argued that differences in respondent type are not as applicable as may be seen in a survey where some participants responded early, whereas others received several reminders and mail -outs before responding. Analyses were undertaken treating the six postings as separate groups to determine any potential differences by respondent type. All groups were similar in claiming that oral communication in general was either ‘essential’ or ‘very important’ in the accountancy profession. Furthermore, oral communication skill was ‘always’ important as a hiring factor for all mail-out groups. When comparing each group on importance and frequency of communication skills using a Kruskall-Wallis test, only one significant difference was found for frequency of listening skills seen in new graduates, x2  ¼ 11.60, P ,0.05. Post- hoc Mann-Whitney U tests subsequently revealed no significant differences in frequency of listening skills seen in new graduates between any of the six groups (using a Bonferroni correction). While the questionnaires were addressed to the Practice Managers of each organis- ation, respondents revealed a degree of variability. The majority of completed question- naires were anonymous, but the respondents who identified themselves ranged from partners in large firms, to senior employees in very small firms, to Human Resources directors. 3.2Interviews The second phase of the study involved employer interviews. Forty-five questionnaire respondents volunteered to be contacted for follow-up interviews, and 19 volunteers could subsequently be contacted by telephone for complete interviews. The interviewee sample size was considered adequate due to its purposive nature and the recent finding that, within such samples, data saturation (including metathemes and subthemes) occurs within the first 12 interviews (Guest, Bunce and Johnson, 2006). It was intended that the qualitative data from interviews would triangulate and extend conclusions arising from analysis of the quantitative data. The interview data incorporated into the study an ethnographic element, ‘thick description, a rich, detailed description of specifics’ (Neuman, 2003, p.  367), which helped produce more robust and credible conclusions. Telephone interviews were conducted between October and December 2008. Intervie- wees ranged from accountancy practice managers to sole practitioners, to partners in large firms. The semi-structured interviews ranged in length from 15 to 45 minutes and sought clarification of a number of issues arising from the questionnaire data, including the impli- cations of globalisation for oral communication in accountancy, the impact of new technologies and the importance of telephone skills, the centrality of listening skills, and the desirability of presentation skills for graduates new to the accountancy workplace. 3.3Data Analysis Once the data from the questionnaires was collated, statistical analysis was performed using SPSS. Mean and median scores were calculated with regard to the importance scores given to each individual oral communication skill, and to the frequency scores (how often each skill is observed in new graduate hires). Each mean was the product of the addition of all the individual importance or frequency scores for each communication skill, divided by the sample size. The standard deviation (SD) of each mean score, as well as the inter-quartile range for the median, was also calculated to indicate the relative spread of responses, with higher figures equating to wider ranges of scores. Owing to a number of missing responses, the denominator of responses to each question shows some variation. As the skill variables violated the assumption of normality (expected given the general level of agreement in employers’ perceptions), non-parametric tests were used. Where relevant, all assumptions of the named tests below were met. 282F. E. Gray and N. Murray As mentioned in 3.1, Section B of the questionnaire invited respondents to write in any further oral communication skills which they felt were important for new accountancy graduates to possess, distinct from the 27 skills listed. Comments identifying additional skills were received from 36 respondents; these comments were recorded and analysed for thematic consistency. Once the interviews were transcribed, themes were also  identified and analysed. Grounded theory was applied to analyse these themes, that is, inductive analysis in which data produce meanings, rather than meanings being applied from exterior theory (Strauss and Corbin, 2000). 4.Findings 4.1Research Objective 1: How Much Importance do New Zealand Accountancy Employers Place on Oral Communication Skills in the New Graduates they Hire? The questionnaire data presented a clear answer to the first research question. Oral communication skill in general was considered to be ‘essential’ in a new graduate by 49.6% (n  ¼ 133) of respondents; a further 41.4% reported it to be ‘very important’. On a rating scale from 1 to 5, where 1 was ‘not important’ and 5 was ‘essential’, the overall mean for oral communication skill in general was 4.39 (Md  ¼ 4.00). A Kruskal- Wallis test found no significant difference in the importance value assigned to oral communication skill depending on the size of the organisation, x2(4)  ¼ 5.48, p . 0.05. During the second phase of the study, interviewees strongly reiterated the perceived importance of oral communication skill: CL called oral communication ‘a career divider,’ meaning it was indispensable to success within accountancy, and EK labelled strong oral communication ‘a distinguishing factor’ setting goo d accountants apart from the mediocre. SWS stated: ‘Being able to communicate is a number one priority .. . [and] it’s going to get more and more important.’ Interview data also supported the signifi- cance of a theme that emerged from written-in comments in the questionnaire: the impor- tance of oral communication skills in accountancy is perceived to be increasing rapidly as a direct result of globalisation, and an increased speaking flexibility and cross-cultural adaptability are considered particularly important in this context. Reporting that they ‘always’ take oral communication skill into account in hiring decisions were 64.1% (n  ¼ 131) of questionnaire respondents (a total of 90.8% reported this to be a hiring factor either ‘always’ or ‘often’). RT stated that strong oral communi- cation skills often proved the decisive factor in a hiring decision: The person who presents well †¦ verbally, if you had to toss a coin between two of them, same grades and all that, the one who can communicate better, you’d give it to that person I think. [.. .] It has to be one of the most powerful strengths or powerful weaknesses that people have. No questionnaire respondents reported ‘never’ taking an applicant’s oral communi- cation skills into account in the hiring process, and several interviewees reported incorpor- ating specific checks of a candidate’s oral competency into their hiring process. For example, TB stated that he telephones all job applicants prior to an in-office interview, in order to gauge their skills in speaking on the telephone. 4.2Research Objective 2: What Specific Kinds of Oral Communication Skills are required by New Zealand Accountancy Employers? Figure 1. Perceived importance of communication skills by perceived frequency of new graduate ability  importance of the individual communication skills against the perceived frequency with which these skills are seen in new graduates. Figure 1 shows that the importance and fre- quency measures follow a similar pattern. This may reflect the influence of the workplace in focussing on developing certain communication competencies in new graduates, or hiring based on those competencies being present to a certain degree. However, there is still an obvious gap between the importance of each skill and the degree to which it is seen in new graduates. 4.2.1Listening skills.On a rating scale from 1 to 5, where 1 was ‘not  important’ and 5 was ‘essential,’ the two skills considered most important were those of listening attentive- ness and listening responsiveness, valued respectively at 4.81 (Md  ¼ 5.00)—82% of respondents ranked listening attentiveness as ‘essential’—and 4.80 (Md  ¼ 5.00)—a further 82% of respondents classifying listening responsiveness as ‘essential’. In sub- sequent interviews, KC described listening to another person as being a more important skill than that of articulating one’s own thoughts: Sometimes, speaking less is better than speaking more. Sometimes you have to have more listening ability. That listening ability will give you the timing of when to say things and when not to say things.. .. A number of interviewees linked listening skill to a related set of competencies concern- ing a speaker’s ability to create rapport and adjust to audiences’ needs. These interviewees spoke of the need for accountancy professionals to communicate with others (clients, colleagues, and managers) ‘in their own language.’ We learn to use sometimes slightly different language in order to be able to communicate to different people and that’s certainly part of our job when we’re in a service industry like 284F. E. Gray and N. Murray  accountancy. We need to talk to people in their language and us[e] words and conduct that they are comfortable with (BR; emphasis added). It’s important to understand your client so that †¦ you’re speaking almost in ‘like language’ so that you know who you are talking to [and] you know they are understanding (SWS; emphasis added). I think it’s a horses for courses [principle], you’ve got to know†¦ your clients or the people you’re dealing with. If you happen to know someone didn’t like a certain style or you could pick from their responses †¦ [then] you reply with like with like (DW; emphasis added). JC mentioned adjusting vocabulary and PW mentioned adjusting message  channel, in relation to the particular needs of the audience. MT emphasised the importance for accountancy graduates to gauge appropriateness of language: They’ve got to realise that when they’re dealing with clients, or senior members of organis- ations, that they’ve got to communicate it appropriately and not in a manner that they may always communicate with their friends or colleagues. Interviewees agreed that this kind of reflective adjustment to an audience’s preferred register is dependent on a speaker’s ability to listen and make appropriate communicative changes. 4.2.2 Vocabulary and slang. Several individual oral communication skills identified in the questionnaire concerned engaging in dialogue and using language and channels preferred by the communication partner. These included ‘explaining or making a topic intelligible’ to colleagues (x  ¼ 4.28, Md  ¼ 4.00, ranked ninth); ‘giving feedback’ to clients: (x  ¼ 4.17, Md  ¼ 4.00, ranked 13th); and ‘using appropriate vocabulary for the audience’, a general audience skill: (x  ¼ 4.21, Md  ¼ 4.00, ranked 10th). Follow-up inter- view questions seeking more information concerning the importance of explanatory and vocabulary skills elicited a number of specific concerns with the use of slang by new accountancy graduates. TO stated: ‘A lot of them have devolved into .. . use of a lot of colloquialisms that may not be acceptable to the older generation.’ According to NM, overly casual language destroys credibility. It’s hard enough for a young person to break in and to be heard, I guess in a business sense when you’re trying to sell to, I guess older people or experienced people. If you come out with schoolyard slang, you don’t stand a chance. Interviews emphasised the desirability in new graduates of a wide-ranging and flexible vocabulary (described by one interviewee as a mental ‘drop-down menu’ of words), oper- ating in tandem with the ability to access the  correct level of spoken formality. After listening attentiveness and listening responsiveness, questionnaire results ident- ified the next five most highly valued individual oral communication skills as being: ‘Con- veying professional attitude of respect and interest in clients’ (x  ¼ 4.68, Md  ¼ 5.00); ‘Asking for clarification or feedback from management’ (x  ¼ 4.57, Md  ¼ 5.00); ‘Speaking on the telephone/making conference calls with clients’ (x  ¼ 4.53, Md  ¼ 5.00); ‘Describ- ing situations accurately and precisely to superior(s)’ (x  ¼ 4.47, Md  ¼ 5.00); and ‘Convey- ing a knowledgeable and confident demeanour to clients’ (x  ¼ 4.45, Md  ¼ 5.00). Please see Table 1 for a complete record of the average and median importance values accorded to each oral communication skill, as well as the reported mean and median frequency with which each skill was found in new accountancy graduates (see also, Gray, 2010).

Saturday, September 28, 2019

The Hunters: Phantom Chapter 2

Dear Diary, I AM HOME! I can hardly dare to believe it, but here I am. I woke with the strangest feeling. I didn't know where I was and just lay here smelling the clean cotton-and-fabric-softener scent of the sheets, trying to figure out why everything looked so familiar. I wasn't in Lady Ulma's mansion. There, I had slept nestled in the smoothest satin and softest velvet, and the air had smelled of incense. And I wasn't at the boardinghouse: Mrs. Flowers washes the bedding there in some weird-smelling herbal mixture that Bonnie says is for protection and good dreams. And suddenly, I knew. I was home. The Guardians did it! They brought me home. Everything and nothing has changed. It's the same room I slept in from when I was a tiny baby: my polished cherry-wood dresser and rocking chair; the little stuffed black-and-white dog Matt won at the winter carnival our junior year perched on a shelf; my rolltop desk with its cubbyholes; the ornate antique mirror above my dresser; and the Monet and Klimt posters from the museum exhibits Aunt Judith took me to in Washington, DC. Even my comb and brush are lined up neatly side by side on my dresser. It's all as it should be. I got out of bed and used a silver letter opener from the desk to pry up the secret board in my closet floor, my old hiding place, and I found this diary, just where I hid it so many months ago. The last entry is the one I wrote before Founder's Day back in November, before I†¦ died. Before I left home and never came back. Until now. In that entry I detailed our plan to steal back my other diary, the one Caroline took from me, the one that she was planning to read aloud at the Founder's Day pageant, knowing it would ruin my life. The very next day, I drowned in Wickery Creek and rose again as a vampire. And then I died again and returned as a human, and traveled to the Dark Dimension, and had a thousand adventures. And my old diary has been sitting right here where I left it under the closet floor, just waiting for me. The other Elena, the one that the Guardians planted in everyone's memories, was here all these months, going to school and living a normal life. That Elena didn't write here. I'm relieved, really. How creepy would it be to see diary entries in my handwriting and not remember any of the things they recounted? Although that might have been helpful. I have no idea what everyone else in Fell's Church thinks has been happening in the months since Founder's Day. The whole town of Fell's Church has been given a fresh start. The kitsune destroyed this town out of sheer malicious mischief. Pitting children against their parents, making people destroy themselves and everyone they loved. But now none of it ever happened. If the Guardians made good on their word, everyone else who died is now alive again: poor Vickie Bennett and Sue Carson, murdered by Katherine and Klaus and Tyler Smallwood back in the winter; disagreeable Mr. Tanner; those innocents that the kitsune killed or caused to be killed. Me. All back again, all starting over. And, except for me and my closest friends – Meredith, Bonnie, Matt, my darling Stefan, and Mrs. Flowers – no one else knows that life hasn't gone on as usual ever since Founder's Day. We've all been given another chance. We did it. We saved everyone. Everyone except Damon. He saved us, in the end, but we couldn't save him. No matter how hard we tried or how desperately we pleaded, there was no way for the Guardians to bring him back. And vampires don't reincarnate. They don't go to Heaven, or Hell, or any kind of afterlife. They just†¦ disappear. Elena stopped writing for a moment and took a deep breath. Her eyes fil ed with tears, but she bent over the diary again. She had to tel the whole truth if there was going to be any point to keeping a diary at al . Damon died in my arms. It was agonizing to watch him slip away from me. But I'll never let Stefan know how I truly felt about his brother. It would be cruel – and what good would it do now? I still can't believe he's gone. There was no one as alive as Damon – no one who loved life more than he did. Now he'll never know – At that moment the door of Elena's bedroom suddenly flew open, and Elena, her heart in her throat, slammed the diary shut. But the intruder was only her younger sister, Margaret, dressed in pink flower-printed pajamas, her cornsilk hair standing straight up in the middle like a thrush's feathers. The five-year-old didn't decelerate until she was almost on top of Elena – and then she launched herself at her through the air. She landed squarely on her older sister, knocking the breath out of her. Margaret's cheeks were wet, her eyes shining, and her little hands clutched at Elena. Elena found herself holding on just as tightly, feeling the weight of her sister, inhaling the sweet scent of baby shampoo and Play-Doh. â€Å"I missed you!† Margaret said, her voice on the verge of sobbing. â€Å"Elena! I missed you so much!† â€Å"What?† Despite her effort to make her voice light, Elena could hear it shaking. She realized with a jolt that she hadn't seen Margaret – really seen her – for more than eight months. But Margaret couldn't know that. â€Å"You missed me so much since bedtime that you had to come running to find me?† Margaret drew slightly away from Elena and stared at her. Margaret's five-year-old clear blue eyes had a look in them, an intensely knowing look, that sent a shiver down Elena's spine. But Margaret didn't say a word. She simply tightened her grip on Elena, curling up and letting her head rest on Elena's shoulder. â€Å"I had a bad dream. I dreamed you left me. You went away.† The last word was a quiet wail. â€Å"Oh, Margaret,† Elena said, hugging her sister's warm solidity, â€Å"it was only a dream. I'm not going anywhere.† She closed her eyes and held on to Margaret, praying her sister had truly only had a nightmare, and that she hadn't slipped through the cracks of the Guardians' spel . â€Å"Al right, cookie, time to get a move on,† said Elena after a few moments, gently tickling Margaret's side. â€Å"Are we going to have a fabulous breakfast together? Shal I make you pancakes?† Margaret sat up then and gazed at Elena with wide blue eyes. â€Å"Uncle Robert's making waffles,† she said. â€Å"He always makes waffles on Sunday mornings. Remember?† Uncle Robert. Right. He and Aunt Judith had gotten married after Elena had died. â€Å"Sure, he does, bunny,† she said lightly. â€Å"I just forgot it was Sunday for a minute.† Now that Margaret had mentioned it, she could hear someone down in the kitchen. And smel something delicious cooking. She sniffed. â€Å"Is that bacon?† Margaret nodded. â€Å"Race you to the kitchen!† Elena laughed and stretched. â€Å"Give me a minute to wake al the way up. I'l meet you down there.† I'll get to talk to Aunt Judith again, she realized with a sudden burst of joy. Margaret bounced out of bed. At the door, she paused and looked back at her sister. â€Å"You real y are coming down, right?† she asked hesitantly. â€Å"I real y am,† Elena said, and Margaret smiled and headed down the hal . Watching her, Elena was struck once more by what an amazing second chance – third chance, real y – she'd been given. For a moment Elena just soaked in the essence of her dear, darling home, a place she'd never thought she'd live in again. She could hear Margaret's light voice chattering away happily downstairs, the deeper rumble of Robert answering her. She was so lucky, despite everything, to be back home at last. What could be more wonderful? Her eyes fil ed with tears and she closed them tightly. What a stupid thing to think. What could be more wonderful? If the crow on her windowsil had been Damon, if she'd known that he was out there somewhere, ready to flash his lazy smile or even purposely aggravate her, now that would have been more wonderful. Elena opened her eyes and blinked hard several times, wil ing the tears away. She couldn't fal apart. Not now. Not when she was about to see her family again. Now she would smile and laugh and hug her family. Later she would col apse, indulging the sharp ache inside her, and let herself sob. After al , she had al the time in the world to mourn Damon, because losing him would never, ever stop hurting.

Friday, September 27, 2019

Viuses are Non-living particles Essay Example | Topics and Well Written Essays - 250 words

Viuses are Non-living particles - Essay Example The modes of transfer of viruses from one person to the other vary significantly. Viruses can be spread through vomits, coughs, sneezes as well as bites from infected organisms (Shors, 4). There are several reasons why viruses are included in biology even though they are non-living. One of the reasons why viruses are included in biology is the fact that they affect living organisms in various ways (Mettenleiter & Francisco, 73 ). Viruses are always associated with several serious diseases in living organisms. Viruses are known to be pathogenic to human beings. They can lead to alteration of the activities of the cells that they have invaded (Shors, 54). This is because viruses are only active when they are inside living cells. Viruses also have the ability to attack as well as infect bacterial cells. These are some of the reasons why viruses are included in biology. Treatment of viral infections is always very difficult using antibiotics. This is because viruses always hide inside the cells (Rogers, 75). This presents a big challenge for the antibiotics to reach them. Therefore, treating viral infections with antibodies is difficult. In addition, the nature of viruses makes it difficult to treat them with antibiotics. Viruses have simple structures. As such they use their host cells’ structures to accomplish their activities. This makes it ineffective to use antibiotics to cure

Thursday, September 26, 2019

Was Deng Xiaoping's Foreign Policy a Success or a Failure Research Paper

Was Deng Xiaoping's Foreign Policy a Success or a Failure - Research Paper Example Though China fought with the US in Korea and in case of Taiwan in his period he was successful in being a strategic partner for the US and achieving MFN status for his country. Though Korea and Japan are trade partners for the US in Asia, the policies of the US regarding China even dominated election manifesto of that Country. When discussing the foreign policy of Deng Xiao Ping, it is reasonable to mention about the US. The underlying reason is that in the post-cold war period, US emerged as a single superpower and any country’s foreign policy was compelled to keep the US in consideration if it wants to be a major partner in world trade. Deng’s policy was the matter of discussion because China developed links with the US despite confrontation in past and present (Taiwan). The significant feature in the Deng’s foreign policy is recognizing the US as a sole superpower in the post-cold war period. The growth of China compelled the US to treat human rights and econo mic benefits separately. Development of Sino US relations: From the date of sworn in of George Bush in 1989 till the end of the two-term presidency of Bill Clinton Sino American relations took a dramatic change. Bush even visited China before visiting Europe to state the new priorities and China reciprocated in the same way US responses.1 The communication gap between China and the Soviet Union, the downward trend of Soviet Union’s economy, George Bush’s diplomacy in meeting China’s leadership before Gorbachev met them made this foreign policy a successful thing for PRC (People's Republic of China). In the aftermath of the Tiananmen Square incident, China’s top leadership recognized that the US has its own compulsions regarding the moral and human values. From that point in time, both the countries started responding cautiously to each other’s acts and deeds.  

Empowerment in the Management Process Assignment

Empowerment in the Management Process - Assignment Example The first step of ensuring structured empowerment is through rewarding employees. Employees who work harder and perform better are given rewards such as bonuses or travel packages by the management. This, in turn, motivates the employees who work hard in ensuring the organization’s success (Blanpain 156). The second step the management can follow in ensuring success is through empowerment. Here, the management gives employees the power to air out their views, which can contribute towards the organization’s objectives. The employees give their views without any fear of victimization by the management (Blanpain 158). The third step involves training employees on the essentials pertaining to daily operations in the organization. Employees are trained so that they readily handle an emergency without seeking consultations from the management (Blanpain 156). The fourth and final step is organizational support. The employees become part owners of the organization, as they are allowed to own shares. The organization can also provide employees with moral or financial support in times of need (Blanpain 156).   Ã‚  Ã‚  

Wednesday, September 25, 2019

Narrative Exposition Essay Example | Topics and Well Written Essays - 1250 words

Narrative Exposition - Essay Example ds every single day, without knowing how much force they had in his life; simple things like taking the bus to work or to the library, cleaning up the dishes at home, everything was done in a very mundane manner because he was getting very bored with living his life. He wanted something new to be offered to him without realizing that only he could make the difference. Academics was something that his parents put a great deal of pressure upon; they had invested a great amount of money for the purpose of John’s education and thus wanted him to excel more than he personally wanted to. John was never good in studies, but he always spent time trying to make his parents happy by trying his best to get good grades. The high school he attended had a number of clubs and associations attached with its prestigious name and as students John and his friends were always encouraged to be a part of them. One fine day, an announcement was made regarding the elimination of a few clubs that did not have many members or donations to remain as part of the school and had to be scrapped off the list because of the decisions taken by a few faculty members who did not have time to invest in the same. This was a social service unit that did not have too many students as a part of it and thus the student body always urged students to join. The main aim of the club w as to help the special children or differently-abled children that lived in and around parts of the city. However, the club was never able to attract a lot of attention towards itself because not everyone wanted to become a part of a social unit designed for the welfare of differently-abled children. A few days later upon looking at the notice of this club, John and his friends went to a nearby cafe to spend some time and as they were happily sipping their lattes, John’s eyes happened to glance over a child on the street; the child seemed helpless and restless and his mother was scolding him. They entered the cafe and

Tuesday, September 24, 2019

The future of RFID protocols Essay Example | Topics and Well Written Essays - 250 words

The future of RFID protocols - Essay Example In terms of necessity, each input assigned to an RFID protocol can be acquired from computations that can only be conducted by parallel RFID tags partaking in the evidence (Peris-Lopez et al., 2011, p. 843). This ability will assure the interconnection of the tokens produced in the course of the evidence, which only the verifier can terminate within a given period. RFID tags should entail different, untraceable, and masked identifiers during every protocol implementation process (Srivastava, n.d., p. 4). Including arbitrary figures appears suitable for developing privacy-secured identifiers although it does not assure immunity against privacy hacks for suggested RFID protocols. RFID protocols should have supreme matching capabilities. For instance, when RFID tags are unable to authenticate their fitting in a certain group, separate tags can be members of a proof. As a result, only the verifier would detect the tags’ failure when sent the evidence (Peris-Lopez et al., 2011, p. 843). RFID protocols should also use encoded versions of timestamps. Verifiers should compute secure timestamps using their abiding secret input. I think a future that employs these potentials of RFID protocols will see a rise in â€Å"smart† products and smarter electronics. For instance, RFID protocols that reach these potentials should be able to tag smart clothes or machines at a store (Srivastava, n.d., p. 9). Peris-Lopez, P, Orfila, A, Hernandez-Castro, JC, van der Lubbe, JCA 2011, ‘Flaws on RFID grouping-proofs. Guidelines for future sound protocols,’ Journal of Network and Computer Applications, vol. 34, pp.

Monday, September 23, 2019

ABC Health Care Research Paper Example | Topics and Well Written Essays - 1500 words

ABC Health Care - Research Paper Example The company is losing its hold on the market, as well as missing income flows and revenues from the poor quality of healthcare networks currently operated by the company. As such, the main aim of this analysis of the requirements of technical analysis of the healthcare is to come up with new ways and strategies that would enable the company make the best out of its networks, as is the case for both its trusted as well as untrusted clients. This is a very critical aspect of the new design development as it enables the company to maintain high security levels. As such, this control of accessibility for both legitimate as well as malicious users of the system forms the utmost importance of the safety and security of the management system of ABC Health Care. The threat that the company faces through the usage of improper management systems does not remain solely to the outside malicious users. However, this also relates to the legitimate users engages in the illegitimate activities. The securities of the company’s website as well as other critical factors that affect the normal operations of the business are critical in maintaining the security of all systems. The new design of network development would include a high-level performance through the incorporation of consistent delivery system. The new design should include proper support systems of the business as well as bridge a balance the security requirements without introduction of significant overhead and complexities that may arise in network use and development. Other important aspects that the new design of network should address include the possibility of maintenance and enhancement of security without incurring a significant increase in the overheads of management or other related complexities. This also incorporates the implementation of systems that are supported by the industry, such as meeting the appropriate standards set by the industry, as well as being scalable and tolerant to faults. The i mplementation of the designs should also assist in ensuring compliance with all the applicable regulations within the market as well as within the industry. To close it up, the system should also have proper access control for both legitimate as well as malicious users. In order to achieve maximum success through the proper usage of the network systems of the ABC Health Care, the analysts should consider the all the related factors to the development of a consistent network system that ensures proper returns as well as provide its clients with the best service deliveries. In addition, the company should also include both internal as well external aspects of network development in improving its technical designs. This is through the considerations that the untrusted aspects of network connectivity would include connectivity of users to the internet, whereas the trusted network would mainly deal with the purpose of supporting all business functions, as well as ensuring that the compan y overcomes it current flaws in network connectivity. Some of the composite business function that this new vision should address would include the suppliers of the company, as well as the partners. These persons or groups have a secure business relationship with the company and assist in its day-to-day operations for culmination into a successful end of a fiscal year. The system designers can also come up with a Network Intrusion Prevention System appliance in order to maintain and uphold the security of the health care system. This is a

Sunday, September 22, 2019

Factors of Planning and Other Functions of Management Essay Example for Free

Factors of Planning and Other Functions of Management Essay With over 300,000 people world wide, ATT is truly a global Fortune 500 company with a significant presence in the communication industry. With impressive growth, executives and managers need to develop a strategy that allows ATT to connect with their customers and manage the contributing factors to their success. As stated in the ATT Annual Report (2007), ATT was able to increase their annual income by 98.3%. This amazing growth occurred in all sectors of their revenue stream and made 2007 a historic year financially for ATT. ATT Chairman, CEO and President, Mr. Randall Stephenson also states in the annual report (2007, p. 8) there is one word that best describes what ATT does and it is connected. A simple vision that clearly describes what ATT does for their customers to drive growth in their organization. In order for a company to succeed in todays market, the product appeal to a global audience is imperative. Although ATT did not begin as a business that offered products and services globally, ATTs network now includes 38 internet data centers on four continents across the globe (ATT, 2008). ATT offers a variety of communication products and services that appeal to individuals and companies. The demand for these types of products and services is on the rise, especially within major corporations. Given this demand, ATT has developed and maintained an advanced and powerful communications network. ATT is an industry leader of communication services, which serves millions of individuals and businesses on six continents (ATT, 2008). The economy is an external factor that influences how ATT manages rapid change. For example, with home foreclosures at a record high, the demand for landline telephone service is decreasing. Meanwhile the demand for wireless service is increasing. ATT continues to focus on advancing wireless products (ATT, Vonage, 2008). ATT has acquired many smaller wireless providers, which allows them to become the top provider of wireless services in the United States. Cingular wireless is one of the wireless companies that ATT bought out. After the purchase of Cingular wireless, ATT began, promoting the new ATT, the one-stop shop for all kinds of communications  and entertainment services (Goodbye Cingular, 2007). As early as 1885, ATT began providing telephone service in the United States. To see the vast growth in their technology over the past 100 years is amazing. The service initially started with one-line calls or the ability for only one person to make a telephone call at a time and it now services over 70 million customers. The costs have decreased significantly over the decades as well. In 1892, a long distance phone call from New York to Chicago would cost about $9 for the first five minutes; rather expensive for that period in time. Today, ATT has grown to be the worlds largest communications carrier and provides services for a broad spectrum of customers from residential to commercial, like the Fortune 1000 companies. Other than the typical local and long distance voice services for the residential customer, ATT also provides high speed internet access, home networking, Wi-Fi, and wireless voice and data services. According to ATTs website (2008), they provide businesses with access to one of the worlds most advanced IP networks. ATT provides the corporate community with technologies, such as, Voice over IP (VoIP), enterprise mobility solutions and Virtual Private Network (VPN) connections. To keep up with todays vastly growing field of technology, ATT (2008) †¦recently switched on the nations first coast-to-coast IP/MPLS network†¦ In the United States alone, ATTs wired network encompasses 61.6 million access lines and has 14.2 million high speed internet subscribers. In 2008, ATT plans to expand their current 64,000 Wi-Fi hot spots to more than 70,000 locations also launch more of their multi-screen services. ATT embraces technological innovation to convert ideas rapidly into useful products and services. ATTs management and planning functions focus on the company and its customers while applying principles of sound, responsible and forward-looking stewardship to the needs of society. Today, ATT is rethinking management functions and planning in terms of the Internet and new culture and capabilities. E-business (electronic business), derived from  such terms as e-mail and e-commerce, is the conduct of business on the Internet, not only buying and selling but also servicing customers and collaborating with business partners. E-business allows ATT and other companies to use the Web to buy parts and supplies from other companies, to collaborate on sales promotions, and to participate in joint research. ATTs involvement with technology innovation such as e-business influences a range of criteria, including customer relationship performance, sales-based outcomes, and a general measure of organizational performance. The moderating role of ATTs management teams involvement suggests that management championing the initiatives is crucial for successful results of the e-business market tendencies and new business development possibilities (ATT, 2008). Alexander Graham Bell made the first telephone call to Watson about 150 years ago. One century ago, there were 10,000 telephone companies battling for their share in the voice communication market. ATT battling in the communications market, realized in order to continue innovation, a sustained research and development component was needed. Early in 1925, ATT determined they could not do this alone and made a series of strategic acquisitions and uniform standards. In the late 20th century, ATT acquired Bell Labs that focused on computers, information and communications science. According to ATT (2008), Recognized as a pioneer in the IT revolution of the late 1990s, direction of innovation at ATT Labs influences not only the ways we live and work today but our lives and the workplace of the future. With these guiding principles, our work in development, creativity and innovation lead to improved social, economic and environmental opportunities for ATT communities. ( ¶13)ATT has made significant innovative contributions to the history of American business and global technology. Listed are a few of these accomplishments including:High-fidelity recording (1925), First TV transmission (1927), Trans-Atlantic radiotelephone (1929), Radio astronomy (1933), The transistor (1937), The first computer (1939), The laser (1960), Optical fiber communication (1977), Cellular technology (1983), Speech recognition and synthesis (1992), Voice over IP technology (1995), Quantum computing (1999), Internet Project predictive and proactive  network security (2005) (ATT, 2008) . ATT noted on their website (2008), Despite its pioneering efforts in other areas of the company, including diversity, customer service and human resources, ATTs reputation for innovation remains closely tethered to ATT Labs.( ¶ 4)ATT realizes that diverse, talented and dedicated people is key to the companys success. In fostering diversity and inclusion, ATT has created a better business environment, one that makes the company an employer of choice, a preferred business partner and important contributor to the community. The companys philosophy is to provide employees with continued opportunities to grow and develop their careers. Management is charged with successful implementation of various diversity initiatives as part of this philosophy. ATT leaders are expected to understand the importance of cultural competency. To support this principle, ATT provides career development initiatives. ATTs commitment to diversity remains a top priority for the company. ATTs diverse workforce is an asset to the company and a result of its commitment to recruit and hire the very best talent. ATT currently conducts business in more than 150 languages and advertises in top languages in selected states. ATT leaders and employees practice respect for differences in their daily interactions. By understanding the various regions served, ATT management is better positioned to plan for and meet the unique needs of customers wherever it does business (ATT, 2008). With over 300,000 working for ATT ensuring ethical behavior is very important. Ethics and Governance are the standards in which the company, including all employees, must adhere to in all aspects of conducting business internally and externally. ATT has adopted a simple statement Do what is right as their motto for ethical conduct by all employees and directors. (Governance, 2003-2008)ATT has four guiding principles stated in their Code of Ethics and Guiding Principles manual on how to treat customers, investors and employees. Those principles are; Talk straight and Follow Through, Lead by Example, Work Together, and Deliver our Future. These four statements are the fabric to ATTs principles and make it clear as to what is expected when working for or dealing with ATT. In todays  environment, ethics have become a serious issue. Directors and managers, as well as employees, are becoming more liable with respect to moral decisions they make at work. Enron is an example of how deceit by a few individuals caused such a ripple effect on the finances of many. Companies like ATT need to touch the moral being of each employee to ensure its customers, shareholders and all parties vested in them are not affected by ones poor judgment. In concluding, with this impressive growth, executives and managers needed to develop a strategy that allowed ATT to connect with their customers and manage the contributing factors to their success. Through innovation and diversity, ATT has grown from a company that started with one-line calling to a multi-million conglomerate, servicing millions of customers around the globe. In keeping up with technology and continuing to implement new corporate strategies, ATT will continue to grow both financially and globally. ATT will continue to be a leader in their field for many years to come. References ATT Inc., (2008), All about ATT Company, Retrieved April 8, 2008, from att.comATT Inc. (2007) Annual Report, p. 8, 29. ATT, Inc. (2008), retrieved April 8, 2008, from att.com/gen/investor-relationsATT. (2008). Enterprise Services. Retrieved April 6, 2008, from att.com/gen/general/ATT Governance, Corporate Social Responsibility (2003-2008). ATT Knowledge Venture, Retrieved April 10, 2008, from att.com/corporate/citizenship/htmlATT, Vonage, Comcast spool the economy. (2008, January). TelecomWeb News Break. Retrieved April 6, 2008, ProQuest database, University Library. Goodbye Cingular, hello again ATT; ATTs acquisition of Bell South began process. (2007, May 21). The New York Times, Grand Rapids Press, Grand Rapids, MI, Retrieved April 9, 2008, from ProQuest database, University Library,

Saturday, September 21, 2019

The declaration of independence

The declaration of independence The Declaration of Independence Thomas Jefferson wrote the Declaration of Independence in 1776.   Its purpose was to declare the 13 colonies in America free and independent from Great Britain, get other colonists on board, and to encourage other nations to help them.   Jefferson not only wrote how they were splitting from Britain, but he also gave thorough reasoning as to why they should be allowed to do so.   In order to do that he used deductive logic in this document.   In addition, many people wonder if the declaration had been developed in a different format, such as a series or syllogistic arguments, how persuasive it would be.   From a literary perspective, it would not have been as persuasive as the original document.   Another reason why the declaration is so persuasive is that Jefferson uses friendly, brotherly language to show his unity to them. The reason why the Declaration of Independence is so persuasive is that Jefferson uses deductive arguments, which includes examples of Britains wrong doings, which gives the person reading the document a chance to see exactly why they are breaking from Great Britain.   One of the strongest deductive arguments in the declaration is, â€Å"That to secure these rights, Governments are instituted among men†.   This means that any legitimate government is created to protect peoples rights such as, â€Å"Life, Liberty, and the pursuit of Happiness†.   Throughout the declaration Jefferson shows how Great Britain is not protecting their rights, but interfering with them.   For example, he states how the king keeps sending over soldiers and expects the people to house and feed them.   How would you feel if the government just placed a stranger in your home and told you he could eat your hard-earned food?   These soldiers were also allowed to disobey the laws in the c olonies and not be punished for them.   This is not what you call protecting peoples rights; it is more like invading them.   Another very strong deductive argument in this document is, â€Å"deriving their just power from the consent of the governed†.   This means any power or authority that a government has is given to them by the consent of the people, but this right like many others was abused too.   For instants, Jefferson wrote that they have â€Å"Petitioned for redress† repeatedly, meaning they sent many petitions to the king about many unfair problems in the colonies, wanting to come to some type of agreement.   Nevertheless, the king does not answer them but continues to hurt them.   This shows that the king did not care about the peoples consent; therefore, he is not implicating a just government and they have the right to break free from Great Britain. If the Declaration were developed in a series of syllogistic arguments, it would not be very persuasive on stating why they should split from Britain.   For example, whether the syllogisms were Aristotles or Toulmins form it would not be a very formal format for a government document.   If this document were in syllogisms, there would be many repeated major premises or warrants, which would cause no concision and wordiness.   Syllogisms would be of better use if you were outlining or organizing the declaration into your own understanding. The main thing besides logic that helped the persuade the colonist they had the right to break from Great Britain, was the language in which Jefferson wrote the declaration.   He used words such as brethren, common kindred, and fellow citizen, which implied that they were all in this together.   He even shows them how the colonies have tried their best to avoid violent conflict with Great Britain but the king would not compromise.   For instants, they had sent many petitions to Britain to come to some type of agreement, but the king continued to hurt the colonies.   Jefferson was arguing that they have tried to work with Great Britain but they continue to send mercenaries to kill people, burn down towns, ravage ships, and capture citizens and make them do very immoral things to their own people.   No nation should sit back and let these horrible things happen to them, so by stating these different scenarios it encourages the fellow colonists that it is time to fight for the ir rights. In conclusion, the declaration of independence is a document that jump-started the United States.   It explains why they had to the right to separate from Great Britain, and many unjust actions they inflicted upon the colonies.   The declaration is a very thorough complex document that would not worked in any other format.   If Jefferson would have wrote this document in a different way would we be in the place we are today?

Friday, September 20, 2019

Practices of Agile Methods in Project Management

Practices of Agile Methods in Project Management Abstract This paper describes the practices of agile methods from the viewpoint of project management. The project management techniques are complex processes that require the understanding and coordination of several domains of knowledge. As more and more software projects engage Agile Methods, there are emerging patterns of success and failure. With growing adoption of Agile Methods, project managers increasingly need to understand the applicability to their projects and factors that drive key project performance characteristics. Agile Methods have advantages, especially in accommodating change due to volatile requirements. However, they also present concomitant risks with managing the many dependent pieces of work distributed across a large project. The paper is divided into four parts. In the first part an overview of the project management and its processes and knowledge areas discussed. after that the agile methods discussed following with a short history of RAD(We should mention that just three most used and famous methodologies are discussed). In the second part the project management approaches and a brief definition of each approach are given. In the third part we looked at the agile methodologies from project management areas view such as cost, time, quality and risk management and we compared agile methodologies and we explained their advantages and disadvantages. In the fourth part we discussed about combination of agile methodologies and their utilization in large and complex projects. And finally we propose our own idea about the future of project management in agile methods. Keywords Project Management, Rapid Development Methodologies, Agile Project Management, History of RAD, Project management approaches, Agile Performance Measurement, Investment and Risk, Agile Enterprise Framework, Agile Methodology Fit Introduction What is Project? A human activity that achieves a clear objective against a time scale A project is a one-shot, time-limited, goal-directed, major undertaking, requiring the commitment of varied skills and resources. A project is a temporary endeavor undertaken to create a unique product or service. A project is temporary in that there is a defined start (the decision to proceed) and a defined end (the achievement of the goals and objectives). Ongoing business or maintenance operations are not projects. Energy conservation projects and process improvement efforts that result in better business processes or more efficient operations can be defined as projects. Projects usually include constraints and risks regarding cost, schedule or performance outcome. What is Project Management? Many have attempted to define project management. One example, Oisen,3 referencing views from the 1950s, may have been one of the early attempts. Project Management is the application of a collection of tools and techniques (such as the CPM and matrix organization) to direct the use of diverse resources toward the accomplishment of a unique, complex, one-time task within time, cost and quality constraints. Each task requires a particular mix of theses tools and techniques structured to fit the task environment and life cycle (from conception to completion) of the task. Notice in the definition are included some the success criteria, The Iron triangle. Those criteria for measuring success included in the description used by Oisen3 continue to be used to describe project management today. The British Standard for project management BS60794 1996 defined project management as: The planning, monitoring and control of all aspects of a project and the motivation of all those involved in it to achieve the project objectives on time and to the specified cost, quality and performance. The UK Association of project Management (APM) have produced a UK Body of Knowledge UK (BoK)5 which also provides a definition for project management as: The planning, organization, monitoring and control of all aspects of a project and the motivation of all involved to achieve the project objectives safely and within agreed time, cost and performance criteria. The project manager is the single point of responsibility for achieving this. Other definitions have been offered, Reiss6 suggests a project is a human activity that achieves a clear objective against a time scale, and to achieve this while pointing out that a simple description is not possible, suggests project management is a combination of management and planning and the management of change. Locks7 view was that project management had evolved in order to plan, co-ordinate and control the complex and diverse activities of modern industrial and commercial projects, while Burke8 considers project management to be a specialized management technique, to plan and control projects under a strong single point of responsibility. While some different suggestions about what is project management have been made, the criteria for success, namely cost, time and quality remain and are included in the actual description. Could this mean that the example given to define project management Oisen3 was either correct, or as a discipline, project management has not really changed or developed the success measurement criteria in almost 50 years. Project management is a learning profession. Based upon past mistakes and believed best practice, standards such as BS 60794 and the UK Body of Knowledge5 continue to be developed. But defining project management is difficult, Wirth,9 indicated the differences in content between six countries own versions of BoKs. Turner10 provided a consolidated matrix to help understand and moderate different attempts to describe project management, including the assessment. Turner10 further suggested that project management could be described as: the art and science of converting vision into reality. Note the criteria against which project management is measured is not included in that description. Is there a paradox however in even attempting to define project management? Can a subject which deals with a unique, one-off complex task as suggested as early as Oisen3 be defined? Perhaps project management is simply an evolving phenomena, which will remain vague enough to be non-definable, a flexible attribute which could be a strength. The significant point is that while the factors have developed and been adopted, changes to the success criteria have been suggested but remain unchanged. Could the link be, that project management continues to fail because, included in the definition are a limited set of criteria for measuring success, cost, time and quality, which even if these criteria are achieved simply demonstrate the chance of matching two best guesses and a phenomena correctly. Prior to some undergraduate lectures and workshops about project management, the students were asked to locate some secondary literature describing project management and produce their own definition. While there were some innovative ideas, the overriding responses included the success criteria of cost, time and quality within the definition. If this is the perception about project management we wish those about to work in the profession to have, the rhetoric over the years has worked. Has this ho wever been the problem to realizing more successful projects? To date, project management has had the success criteria focused upon the delivery stage, up to implementation. Reinforced by the very description we have continued to use to define the profession. The focus has been to judge whether the project was done right. Doing something right may result in a project which was implemented on time, within cost and to some quality parameters requested, but which is not used by the customers, not liked by the sponsors and does not seem to provide either improved effectiveness or efficiency for the organization, is this successful project management? Project Management Life Cycle The process flow of Project management processes is shown below. The various elements of project management life cycle are Need identification Initiation Planning Executing Controlling Closing out a) Need Identification The first step in the project development cycle is to identify components of the project. Projects may be identified both internally and externally: Internal identification takes place when the energy manager identifies a package of energy saving opportunities during the day-to-day energy management activities, or from facility audits. External identification of energy savings can occur through systematic energy audits undertaken by a reputable energy auditor or energy service company. In screening projects, the following criteria should be used to rank-order project opportunities. Cost-effectiveness of energy savings of complete package of measures (Internal rate of return, net present value, cash flow, average payback) Sustainability of the savings over the life of the equipment. Ease of quantifying, monitoring, and verifying electricity and fuel savings. Availability of technology, and ease of adaptability of the technology to Indian conditions. Other environmental and social cost benefits (such as reduction in local pollutants, e.g. SOx) b) Initiation Initiating is the basic processes that should be performed to get the project started. This starting point is critical because those who will deliver the project, those who will use the Bureau of Energy Efficiency project, and those who will have a stake in the project need to reach an agreement on its initiation. Involving all stakeholders in the project phases generally improves the probability of satisfying customer requirements by shared ownership of the project by the stakeholders. The success of the project team depends upon starting with complete and accurate information, management support, and the authorization necessary to manage the project. The initiation stage should include a plan that encompasses the following areas: Analyzing the business needs/requirements in measurable goals Reviewing of the current operations Financial analysis of the costs and benefits including a budget Stakeholder analysis, including users, and support personnel for the project Project charter including costs, tasks, deliverables, and schedule c) Planning The planning phase is considered the most important phase in project management. Project planning defines project activities that will be performed; the products that will be produced, and describes how these activities will be accomplished and managed. Project planning defines each major task, estimates the time, resources and cost required, and provides a framework for management review and control. Planning involves identifying and documenting scope, tasks, schedules, cost, risk, quality, and staffing needs. The result of the project planning, the project plan, will be an approved, comprehensive document that allows a project team to begin and complete the work necessary to achieve the project goals and objectives. The project plan will address how the project team will manage the project elements. It will provide a high level of confidence in the organizations ability to meet the scope, timing, cost, and quality requirements by addressing all aspects of the project. Project planning generally consists of determining how to plan (e.g. by level of detail or rolling wave); developing the scope statement; selecting the planning team; identifying deliverables and creating the work breakdown structure; identifying the activities needed to complete those deliverables and networking the activities in their logical sequence; estimating the resource requirements for the activities; estimating time and cost for activities; developing the schedule; developing the budget; risk planning; gaining formal approval to begin work. Additional processes, such as planning for communications and for scope management, identifying roles and responsibilities, determining what to purchase for the project and holding a kick-off meeting are also generally advisable. For new product development projects, conceptual design of the operation of the final product may be performed concurrent with the project planning activities, and may help to inform the planning team when identifying deliverables and planning activities d) Executing Once a project moves into the execution phase, the project team and all necessary resources to carry out the project should be in place and ready to perform project activities. The project plan is completed and base lined by this time as well. The project team and the project managers focus now shifts from planning the project efforts to participating, observing, and analyzing the work being done. The execution phase is when the work activities of the project plan are executed, resulting in the completion of the project deliverables and achievement of the project objective(s). This phase brings together all of the project management disciplines, resulting in a product or service that will meet the project deliverable requirements and the customers need. During this phase, elements completed in the planning phase are implemented, time is expended, and money is spent. In short, it means coordinating and managing the project resources while executing the project plan, performing the planned project activities, and ensuring they are completed efficiently. e) Monitoring and Controlling Project Control function that involves comparing actual performance with planned performance and taking corrective action to get the desired outcome when there are significant differences. By monitoring and measuring progress regularly, identifying Bureau of Energy Efficiency variances from plan, and taking corrective action if required, project control ensures that project objectives are met. Monitoring and Controlling includes: Measuring the ongoing project activities (where we are); Monitoring the project variables (cost, effort, scope, etc.) against the project management plan and the project performance baseline (where we should be); Identify corrective actions to address issues and risks properly (How can we get on track again); Influencing the factors that could circumvent integrated change control so only approved changes are implemented In multi-phase projects,process also provides feedback between project phases, in order to implement corrective or preventive actions to bring the project into compliance with the project management plan. Project Maintenance is an ongoing process, and it includes: Continuing support of end users Correction of errors Updates of the software over time Monitoring and Controlling cycle In this stage, auditors should pay attention to how effectively and quickly user problems are resolved. Over the course of any construction project, the work scope may change. Change is a normal and expected part of the construction process. Changes can be the result of necessary design modifications, differing site conditions, material availability, contractor-requested changes, value engineering and impacts from third parties, to name a few. Beyond executing the change in the field, the change normally needs to be documented to show what was actually constructed. This is referred to as Change Management. Hence, the owner usually requires a final record to show all changes or, more specifically, any change that modifies the tangible portions of the finished work. The record is made on the contract documents usually, but not necessarily limited to, the design drawings. The end product of this effort is what the industry terms as-built drawings, or more simply, as built. The requirement for providing them is a norm in construction contracts. When changes are introduced to the project, the viability of the project has to be re-assessed. It is important not to lose sight of the initial goals and targets of the projects. When the changes accumulate, the forecasted result may not justify the original proposed investment in the project. f) Closing out Project closeout is performed after all defined project objectives have been met and the customer has formally accepted the projects deliverables and end product or, in some instances, when a project has been cancelled or terminated early. Although, project closeout is a routine process, it is an important one. By properly completing the project closeout, organizations can benefit from lessons learned and information compiled. The project closeout phase is comprised of contract closeout and administrative closure. This phase consists of: Project close: Finalize all activities across all of the process groups to formally close the project or a project phase Contract closure: Complete and settle each contract (including the resolution of any open items) and close each contract applicable to the project or project phase Project Management Knowledge Areas with the Related Processes Each of the nine knowledge areas contains the processes that need to be accomplished within its discipline in order to achieve an effective project management program. Each of these processes also falls into one of the five basic process groups, creating a matrix structure such that every process can be related to one knowledge area and one process group. Risk Management Software development projects represent an investment of resources by the projects sponsor, an investment that often yields little or no return. The Standish Groups Chaos Report 1994 states that fewer than 10% of software projects in large companies were successful. Medium sized companies do better with 16% of their software projects being successful, and small companies succeed on 28% of their software projects (Standish 1994). Given these statistics it is worthwhile to invest significant effort in Risk Management for software projects. Research at The Standish Group also indicates that smaller time frames, with delivery of software components early and often, will increase the success rate. (Standish 1994). Integration Management Extreme Programming offers nothing to help integrate the efforts of non-software developers. Unfortunately, some advocates of Extreme Programming suggest that the efforts of technical writers, database managers, and quality assurance specialist are not required. In reality, while Extreme Programming does not explicitly describe how to integrate the work of others, the practices do not preclude the ability to integrate with other efforts. Small Releases make Integration Management a more continuous process in contrast to processes that place deployment, documentation, and testing at the end of the schedule. Continuous Integration At a more tactical level, the Extreme Programming practice of Continuous Integration requires that the work of software developers be integrated on a daily basis. While this practice can cause additional overhead for individual developers, it allows the team to identify problems daily that would otherwise become undiscovered rework accumulating until all developers integrate their individual work products. Scope Management Time Management Ask most software development teams for a copy of their project plan and you will receive an activity list formatted as a Gantt chart. Many times these activity lists will describe several phases of activities such as Analysis, Design, Construction, and Testing. Areas of functionality will be broken out under these headings in order to assign them to specific programmers, but seldom are the assignments identified in the Gantt chart clearly traceable back to a Requirement or other specification documents. All too often, the missing item that would help a team improve their planning practices is a well-constructed Work Breakdown Structure. Extreme Programming focuses almost all of its planning efforts on building a thoughtful Work Breakdown Structure and its constituent Work Packages. Extreme Programming does not teach Work Breakdown Structures and Work Packages explicitly, however, careful study of the Story Cards used in Extreme Programming reveals that they are almost identical to Work Packages in their key attributes. Human Resources Management Often one of the most challenging aspects of project management is managing human resources. For software development projects in particular this includes the complex juggling of technical tasks between individual software developers who have different individual skills, effectively treating each developers assigned tasks as an independent subproject. This type of project plan often suffers from key resource bottlenecks and status meetings reduced to determining which individuals are falling furthest behind. Extreme Programming addresses this head-on by eliminating the dependency on individual developers. Work Packages are scheduled and authorized based on the needs of the business and the users not the needs of the software developers. All developers are cross-trained to work in all areas of the code base. Developers broaden their skills, and project managers stop worrying about keeping individual software developers for the entire duration of the project. The process maintains know ledge of the full code base in the team, not in individuals. Quality Management As programmers move from work authorization to work authorization, and often from one area of the code to another, it is easy to see that maintaining quality in the work product could be challenging. Extreme Programming requires a very disciplined design approach to allow freedom in assigning resources while maintaining high quality. Communications Management When a project manager mentions the need for improved communications on a project, software developers often immediately envision an increased number of meetings and documents. While formal meetings and written documents have their place in a communication plan there are many other tools for facilitation of communication between project participants. The Extreme Programming practices include several simple practices intended to enhance communications. Costs Management Often a Project Manager is evaluated on his or her ability to complete a project within budget. The costs include estimated cost, actual cost and variability. Contingency cost takes into account influence of weather, suppliers and design allowances. How the 80/20 Rule can help a project manager? The 80/20 Rule means that in anything a few (20 percent) are vital and many (80 percent) are trivial. Successful Project Managers know that 20 percent of the work (the first 10 percent and the last 10 percent) consumes 80 percent of your time and resources. The History of RAD Traditional lifecycles devised in the 1970s, and still widely used today, are based upon a structured step-by-step approach to developing systems. This rigid sequence of steps forces a user to sign-off after the completion of each specification before development can proceed to the next step. The requirements and design are then frozen and the system is coded, tested, and implemented. With such conventional methods, there is a long delay before the customer gets to see any results and the development process can take so long that the customers business could fundamentally change before the system is even ready for use. In response to these rigid, cascading, one-way steps of Stagewise or Waterfall Models of development, Barry Boehm, Chief SW Engineer at TRW, introduced his Spiral Model. The Spiral Model is a risk-driven, as opposed to code-driven, approach that uses process modeling rather than methodology phases. Through his model, Boehm first implemented software prototyping as a way of reducing risk. The development process of the Spiral Model separates the product into critical parts or levels while performing risk analyses, prototyping, and the same steps at each of these levels. Similarly, Tom Gilbs Evolutionary Life Cycle is based on an evolutionary prototyping rationale where the prototype is grown and refined into the final product. The work of Boehm and Gilb paved the way for the formulation of the methodology called Rapid Iterative Production Prototyping (RIPP) at DuPont in the mid-to-late 1980s. James Martin then extended the work done at DuPont and elsewhere into a larger, more formalized process, which has become known as Rapid Application Development (RAD). RAD compresses the step-by-step development of conventional methods into an iterative process. The RAD approach thus includes developing and refining the data models, process models, and prototype in parallel using an iterative process. User requirements are refined, a solution is designed, the solution is prototyped, the prototype is reviewed, user input is provided, and the process begins again. What is Agility? There is no Agility for Dummies. Agility isnt a silver bullet. You dont achieve it in five easy steps. So what is it? From one view agility characterized in two statements: Agility is the ability to both create and respond to change in order to profit in a turbulent business environment. Agility is the ability to balance flexibility and stability (Highsmith 2002). In an uncertain and turbulent world, success belongs to companies that have the capacity to create change, and maybe even chaos, for their competitors. Creating change disrupts competitors (and the entire market ecosystem); responding to change guards against competitive thrusts. Creating change requires innovation: developing new products, creating new sales channels, reducing product development time, customizing products for increasingly smaller market segments. In addition, your company must be able to respond quickly to both anticipated and unanticipated changes created by your competitors and customers. An example of a product development effort in which all the aspects of agility come into play is that of small, portable DNA analyzers. These instruments can be used for analyzing suspected bio-terror agents (e.g., anthrax), performing quick medical diagnoses, or undertaking environmental bacterial analysis. These instruments must be accurate, easy to use, and reliable under wide-ranging conditions, and their development depends on breakthroughs in nanotechnology, genome research, and micro-fluidics. Developing these leading-edge products requires blending flexibility and structure, exploring various new technologies, and creating change for competitors by reducing delivery time. These are not projects that can be managed by traditional, prescriptive project management methodologies. Some people mistakenly assume that agility connotes a lack of structure, but the absence of structure, or stability, generates chaos. Conversely, too much structure generates rigidity. Complexity theory tells us that innovation—creating something new in ways that we cant fully anticipate (an emergent result) occurs most readily at the balance point between chaos and order, between flexibility and stability. Scientists believe that emergence, the creation of novelty from agent interaction, happens most readily at this edge of chaos. The idea of enough structure, but not too much, drives agile managers to continually ask the question, How little structure can I get away with? Too much structure stifles creativity. Too little structure breeds inefficiency. This need to balance at the edge of chaos to foster innovation is one reason process-centric methodologies often fail. They push organizations into over-optimization at the expense of innovation. Agile organizations dont get lost in some gray middle ground; they understand which factors require stabilization and which ones encourage exploration. For example, in a high-change product development environment, rigorous configuration management stabilizes and facilitates flexibility just as a focus on technical excellence stabilizes the development effort. Overview and definitions The Agile Movement in software industry saw the light of day with the Agile Software Development Manifesto4 published by a group of software practitioners and consultants in 2001 (Beck et al. 2001; Cockburn 2002a). The focal values honored by the agilists are presented in the following: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan These central values that the agile community adheres to are: First, the agile movement emphasizes the relationship and communality of software developers and the human role reflected in the contracts, as opposed to institutionalized processes and development tools. In the existing agile practices, this manifests itself in close team relationships, close working environment arrangements, and other procedures boosting team spirit. Second, the vital objective of the software team is to continuously turn out tested working software. New releases are produced at frequent intervals, in some approaches even hourly or daily, but more usually bi-monthly or monthly. The developers are urged to keep the code simple, straightforward, and technically as advanced as possible, thus lessening the documentation burden to an appropriate level. Third, the relationship and cooperation between the developers and the clients is given the preference over strict contracts, although the importance of well drafted contracts does grow at the same pace as the size of the software project. The negotiation process itself should be seen as a means of achieving and maintaining a viable relationship. From a business point of view, agile development is focused on delivering business value immediately as the project starts, thus reducing the risks of non-fulfillment regarding the contract. Fourth, the development group, comprising both software developers and customer representatives, should be well-informed, competent and authorized to consider possible adjustment needs emerging during the development process life-cycle. This means that the participants are prepared to make changes and that also the existing contracts are formed with tools that support and allow these enhancements to be made. According to Highsmith and Cockburn (2001, p. 122), what is new about agile methods is not the practices they use, but their recognition of people as the primary drivers of project success, coupled with an intense focus on effectiveness and maneuverability. This yields a new combination of values and principles that define an agile world view. Boehm (2002) illustrates the spectrum of different planning methods with Figure 1, in which hackers are placed at one end and the so called inch-pebble ironbound contractual approach at the opposite end: Hawrysh and Ruprecht (2000) state that a single methodology can not work for the whole spectrum of different projects, but instead the project management should identify the specific nature of the project at hand and then select the bes Practices of Agile Methods in Project Management Practices of Agile Methods in Project Management Abstract This paper describes the practices of agile methods from the viewpoint of project management. The project management techniques are complex processes that require the understanding and coordination of several domains of knowledge. As more and more software projects engage Agile Methods, there are emerging patterns of success and failure. With growing adoption of Agile Methods, project managers increasingly need to understand the applicability to their projects and factors that drive key project performance characteristics. Agile Methods have advantages, especially in accommodating change due to volatile requirements. However, they also present concomitant risks with managing the many dependent pieces of work distributed across a large project. The paper is divided into four parts. In the first part an overview of the project management and its processes and knowledge areas discussed. after that the agile methods discussed following with a short history of RAD(We should mention that just three most used and famous methodologies are discussed). In the second part the project management approaches and a brief definition of each approach are given. In the third part we looked at the agile methodologies from project management areas view such as cost, time, quality and risk management and we compared agile methodologies and we explained their advantages and disadvantages. In the fourth part we discussed about combination of agile methodologies and their utilization in large and complex projects. And finally we propose our own idea about the future of project management in agile methods. Keywords Project Management, Rapid Development Methodologies, Agile Project Management, History of RAD, Project management approaches, Agile Performance Measurement, Investment and Risk, Agile Enterprise Framework, Agile Methodology Fit Introduction What is Project? A human activity that achieves a clear objective against a time scale A project is a one-shot, time-limited, goal-directed, major undertaking, requiring the commitment of varied skills and resources. A project is a temporary endeavor undertaken to create a unique product or service. A project is temporary in that there is a defined start (the decision to proceed) and a defined end (the achievement of the goals and objectives). Ongoing business or maintenance operations are not projects. Energy conservation projects and process improvement efforts that result in better business processes or more efficient operations can be defined as projects. Projects usually include constraints and risks regarding cost, schedule or performance outcome. What is Project Management? Many have attempted to define project management. One example, Oisen,3 referencing views from the 1950s, may have been one of the early attempts. Project Management is the application of a collection of tools and techniques (such as the CPM and matrix organization) to direct the use of diverse resources toward the accomplishment of a unique, complex, one-time task within time, cost and quality constraints. Each task requires a particular mix of theses tools and techniques structured to fit the task environment and life cycle (from conception to completion) of the task. Notice in the definition are included some the success criteria, The Iron triangle. Those criteria for measuring success included in the description used by Oisen3 continue to be used to describe project management today. The British Standard for project management BS60794 1996 defined project management as: The planning, monitoring and control of all aspects of a project and the motivation of all those involved in it to achieve the project objectives on time and to the specified cost, quality and performance. The UK Association of project Management (APM) have produced a UK Body of Knowledge UK (BoK)5 which also provides a definition for project management as: The planning, organization, monitoring and control of all aspects of a project and the motivation of all involved to achieve the project objectives safely and within agreed time, cost and performance criteria. The project manager is the single point of responsibility for achieving this. Other definitions have been offered, Reiss6 suggests a project is a human activity that achieves a clear objective against a time scale, and to achieve this while pointing out that a simple description is not possible, suggests project management is a combination of management and planning and the management of change. Locks7 view was that project management had evolved in order to plan, co-ordinate and control the complex and diverse activities of modern industrial and commercial projects, while Burke8 considers project management to be a specialized management technique, to plan and control projects under a strong single point of responsibility. While some different suggestions about what is project management have been made, the criteria for success, namely cost, time and quality remain and are included in the actual description. Could this mean that the example given to define project management Oisen3 was either correct, or as a discipline, project management has not really changed or developed the success measurement criteria in almost 50 years. Project management is a learning profession. Based upon past mistakes and believed best practice, standards such as BS 60794 and the UK Body of Knowledge5 continue to be developed. But defining project management is difficult, Wirth,9 indicated the differences in content between six countries own versions of BoKs. Turner10 provided a consolidated matrix to help understand and moderate different attempts to describe project management, including the assessment. Turner10 further suggested that project management could be described as: the art and science of converting vision into reality. Note the criteria against which project management is measured is not included in that description. Is there a paradox however in even attempting to define project management? Can a subject which deals with a unique, one-off complex task as suggested as early as Oisen3 be defined? Perhaps project management is simply an evolving phenomena, which will remain vague enough to be non-definable, a flexible attribute which could be a strength. The significant point is that while the factors have developed and been adopted, changes to the success criteria have been suggested but remain unchanged. Could the link be, that project management continues to fail because, included in the definition are a limited set of criteria for measuring success, cost, time and quality, which even if these criteria are achieved simply demonstrate the chance of matching two best guesses and a phenomena correctly. Prior to some undergraduate lectures and workshops about project management, the students were asked to locate some secondary literature describing project management and produce their own definition. While there were some innovative ideas, the overriding responses included the success criteria of cost, time and quality within the definition. If this is the perception about project management we wish those about to work in the profession to have, the rhetoric over the years has worked. Has this ho wever been the problem to realizing more successful projects? To date, project management has had the success criteria focused upon the delivery stage, up to implementation. Reinforced by the very description we have continued to use to define the profession. The focus has been to judge whether the project was done right. Doing something right may result in a project which was implemented on time, within cost and to some quality parameters requested, but which is not used by the customers, not liked by the sponsors and does not seem to provide either improved effectiveness or efficiency for the organization, is this successful project management? Project Management Life Cycle The process flow of Project management processes is shown below. The various elements of project management life cycle are Need identification Initiation Planning Executing Controlling Closing out a) Need Identification The first step in the project development cycle is to identify components of the project. Projects may be identified both internally and externally: Internal identification takes place when the energy manager identifies a package of energy saving opportunities during the day-to-day energy management activities, or from facility audits. External identification of energy savings can occur through systematic energy audits undertaken by a reputable energy auditor or energy service company. In screening projects, the following criteria should be used to rank-order project opportunities. Cost-effectiveness of energy savings of complete package of measures (Internal rate of return, net present value, cash flow, average payback) Sustainability of the savings over the life of the equipment. Ease of quantifying, monitoring, and verifying electricity and fuel savings. Availability of technology, and ease of adaptability of the technology to Indian conditions. Other environmental and social cost benefits (such as reduction in local pollutants, e.g. SOx) b) Initiation Initiating is the basic processes that should be performed to get the project started. This starting point is critical because those who will deliver the project, those who will use the Bureau of Energy Efficiency project, and those who will have a stake in the project need to reach an agreement on its initiation. Involving all stakeholders in the project phases generally improves the probability of satisfying customer requirements by shared ownership of the project by the stakeholders. The success of the project team depends upon starting with complete and accurate information, management support, and the authorization necessary to manage the project. The initiation stage should include a plan that encompasses the following areas: Analyzing the business needs/requirements in measurable goals Reviewing of the current operations Financial analysis of the costs and benefits including a budget Stakeholder analysis, including users, and support personnel for the project Project charter including costs, tasks, deliverables, and schedule c) Planning The planning phase is considered the most important phase in project management. Project planning defines project activities that will be performed; the products that will be produced, and describes how these activities will be accomplished and managed. Project planning defines each major task, estimates the time, resources and cost required, and provides a framework for management review and control. Planning involves identifying and documenting scope, tasks, schedules, cost, risk, quality, and staffing needs. The result of the project planning, the project plan, will be an approved, comprehensive document that allows a project team to begin and complete the work necessary to achieve the project goals and objectives. The project plan will address how the project team will manage the project elements. It will provide a high level of confidence in the organizations ability to meet the scope, timing, cost, and quality requirements by addressing all aspects of the project. Project planning generally consists of determining how to plan (e.g. by level of detail or rolling wave); developing the scope statement; selecting the planning team; identifying deliverables and creating the work breakdown structure; identifying the activities needed to complete those deliverables and networking the activities in their logical sequence; estimating the resource requirements for the activities; estimating time and cost for activities; developing the schedule; developing the budget; risk planning; gaining formal approval to begin work. Additional processes, such as planning for communications and for scope management, identifying roles and responsibilities, determining what to purchase for the project and holding a kick-off meeting are also generally advisable. For new product development projects, conceptual design of the operation of the final product may be performed concurrent with the project planning activities, and may help to inform the planning team when identifying deliverables and planning activities d) Executing Once a project moves into the execution phase, the project team and all necessary resources to carry out the project should be in place and ready to perform project activities. The project plan is completed and base lined by this time as well. The project team and the project managers focus now shifts from planning the project efforts to participating, observing, and analyzing the work being done. The execution phase is when the work activities of the project plan are executed, resulting in the completion of the project deliverables and achievement of the project objective(s). This phase brings together all of the project management disciplines, resulting in a product or service that will meet the project deliverable requirements and the customers need. During this phase, elements completed in the planning phase are implemented, time is expended, and money is spent. In short, it means coordinating and managing the project resources while executing the project plan, performing the planned project activities, and ensuring they are completed efficiently. e) Monitoring and Controlling Project Control function that involves comparing actual performance with planned performance and taking corrective action to get the desired outcome when there are significant differences. By monitoring and measuring progress regularly, identifying Bureau of Energy Efficiency variances from plan, and taking corrective action if required, project control ensures that project objectives are met. Monitoring and Controlling includes: Measuring the ongoing project activities (where we are); Monitoring the project variables (cost, effort, scope, etc.) against the project management plan and the project performance baseline (where we should be); Identify corrective actions to address issues and risks properly (How can we get on track again); Influencing the factors that could circumvent integrated change control so only approved changes are implemented In multi-phase projects,process also provides feedback between project phases, in order to implement corrective or preventive actions to bring the project into compliance with the project management plan. Project Maintenance is an ongoing process, and it includes: Continuing support of end users Correction of errors Updates of the software over time Monitoring and Controlling cycle In this stage, auditors should pay attention to how effectively and quickly user problems are resolved. Over the course of any construction project, the work scope may change. Change is a normal and expected part of the construction process. Changes can be the result of necessary design modifications, differing site conditions, material availability, contractor-requested changes, value engineering and impacts from third parties, to name a few. Beyond executing the change in the field, the change normally needs to be documented to show what was actually constructed. This is referred to as Change Management. Hence, the owner usually requires a final record to show all changes or, more specifically, any change that modifies the tangible portions of the finished work. The record is made on the contract documents usually, but not necessarily limited to, the design drawings. The end product of this effort is what the industry terms as-built drawings, or more simply, as built. The requirement for providing them is a norm in construction contracts. When changes are introduced to the project, the viability of the project has to be re-assessed. It is important not to lose sight of the initial goals and targets of the projects. When the changes accumulate, the forecasted result may not justify the original proposed investment in the project. f) Closing out Project closeout is performed after all defined project objectives have been met and the customer has formally accepted the projects deliverables and end product or, in some instances, when a project has been cancelled or terminated early. Although, project closeout is a routine process, it is an important one. By properly completing the project closeout, organizations can benefit from lessons learned and information compiled. The project closeout phase is comprised of contract closeout and administrative closure. This phase consists of: Project close: Finalize all activities across all of the process groups to formally close the project or a project phase Contract closure: Complete and settle each contract (including the resolution of any open items) and close each contract applicable to the project or project phase Project Management Knowledge Areas with the Related Processes Each of the nine knowledge areas contains the processes that need to be accomplished within its discipline in order to achieve an effective project management program. Each of these processes also falls into one of the five basic process groups, creating a matrix structure such that every process can be related to one knowledge area and one process group. Risk Management Software development projects represent an investment of resources by the projects sponsor, an investment that often yields little or no return. The Standish Groups Chaos Report 1994 states that fewer than 10% of software projects in large companies were successful. Medium sized companies do better with 16% of their software projects being successful, and small companies succeed on 28% of their software projects (Standish 1994). Given these statistics it is worthwhile to invest significant effort in Risk Management for software projects. Research at The Standish Group also indicates that smaller time frames, with delivery of software components early and often, will increase the success rate. (Standish 1994). Integration Management Extreme Programming offers nothing to help integrate the efforts of non-software developers. Unfortunately, some advocates of Extreme Programming suggest that the efforts of technical writers, database managers, and quality assurance specialist are not required. In reality, while Extreme Programming does not explicitly describe how to integrate the work of others, the practices do not preclude the ability to integrate with other efforts. Small Releases make Integration Management a more continuous process in contrast to processes that place deployment, documentation, and testing at the end of the schedule. Continuous Integration At a more tactical level, the Extreme Programming practice of Continuous Integration requires that the work of software developers be integrated on a daily basis. While this practice can cause additional overhead for individual developers, it allows the team to identify problems daily that would otherwise become undiscovered rework accumulating until all developers integrate their individual work products. Scope Management Time Management Ask most software development teams for a copy of their project plan and you will receive an activity list formatted as a Gantt chart. Many times these activity lists will describe several phases of activities such as Analysis, Design, Construction, and Testing. Areas of functionality will be broken out under these headings in order to assign them to specific programmers, but seldom are the assignments identified in the Gantt chart clearly traceable back to a Requirement or other specification documents. All too often, the missing item that would help a team improve their planning practices is a well-constructed Work Breakdown Structure. Extreme Programming focuses almost all of its planning efforts on building a thoughtful Work Breakdown Structure and its constituent Work Packages. Extreme Programming does not teach Work Breakdown Structures and Work Packages explicitly, however, careful study of the Story Cards used in Extreme Programming reveals that they are almost identical to Work Packages in their key attributes. Human Resources Management Often one of the most challenging aspects of project management is managing human resources. For software development projects in particular this includes the complex juggling of technical tasks between individual software developers who have different individual skills, effectively treating each developers assigned tasks as an independent subproject. This type of project plan often suffers from key resource bottlenecks and status meetings reduced to determining which individuals are falling furthest behind. Extreme Programming addresses this head-on by eliminating the dependency on individual developers. Work Packages are scheduled and authorized based on the needs of the business and the users not the needs of the software developers. All developers are cross-trained to work in all areas of the code base. Developers broaden their skills, and project managers stop worrying about keeping individual software developers for the entire duration of the project. The process maintains know ledge of the full code base in the team, not in individuals. Quality Management As programmers move from work authorization to work authorization, and often from one area of the code to another, it is easy to see that maintaining quality in the work product could be challenging. Extreme Programming requires a very disciplined design approach to allow freedom in assigning resources while maintaining high quality. Communications Management When a project manager mentions the need for improved communications on a project, software developers often immediately envision an increased number of meetings and documents. While formal meetings and written documents have their place in a communication plan there are many other tools for facilitation of communication between project participants. The Extreme Programming practices include several simple practices intended to enhance communications. Costs Management Often a Project Manager is evaluated on his or her ability to complete a project within budget. The costs include estimated cost, actual cost and variability. Contingency cost takes into account influence of weather, suppliers and design allowances. How the 80/20 Rule can help a project manager? The 80/20 Rule means that in anything a few (20 percent) are vital and many (80 percent) are trivial. Successful Project Managers know that 20 percent of the work (the first 10 percent and the last 10 percent) consumes 80 percent of your time and resources. The History of RAD Traditional lifecycles devised in the 1970s, and still widely used today, are based upon a structured step-by-step approach to developing systems. This rigid sequence of steps forces a user to sign-off after the completion of each specification before development can proceed to the next step. The requirements and design are then frozen and the system is coded, tested, and implemented. With such conventional methods, there is a long delay before the customer gets to see any results and the development process can take so long that the customers business could fundamentally change before the system is even ready for use. In response to these rigid, cascading, one-way steps of Stagewise or Waterfall Models of development, Barry Boehm, Chief SW Engineer at TRW, introduced his Spiral Model. The Spiral Model is a risk-driven, as opposed to code-driven, approach that uses process modeling rather than methodology phases. Through his model, Boehm first implemented software prototyping as a way of reducing risk. The development process of the Spiral Model separates the product into critical parts or levels while performing risk analyses, prototyping, and the same steps at each of these levels. Similarly, Tom Gilbs Evolutionary Life Cycle is based on an evolutionary prototyping rationale where the prototype is grown and refined into the final product. The work of Boehm and Gilb paved the way for the formulation of the methodology called Rapid Iterative Production Prototyping (RIPP) at DuPont in the mid-to-late 1980s. James Martin then extended the work done at DuPont and elsewhere into a larger, more formalized process, which has become known as Rapid Application Development (RAD). RAD compresses the step-by-step development of conventional methods into an iterative process. The RAD approach thus includes developing and refining the data models, process models, and prototype in parallel using an iterative process. User requirements are refined, a solution is designed, the solution is prototyped, the prototype is reviewed, user input is provided, and the process begins again. What is Agility? There is no Agility for Dummies. Agility isnt a silver bullet. You dont achieve it in five easy steps. So what is it? From one view agility characterized in two statements: Agility is the ability to both create and respond to change in order to profit in a turbulent business environment. Agility is the ability to balance flexibility and stability (Highsmith 2002). In an uncertain and turbulent world, success belongs to companies that have the capacity to create change, and maybe even chaos, for their competitors. Creating change disrupts competitors (and the entire market ecosystem); responding to change guards against competitive thrusts. Creating change requires innovation: developing new products, creating new sales channels, reducing product development time, customizing products for increasingly smaller market segments. In addition, your company must be able to respond quickly to both anticipated and unanticipated changes created by your competitors and customers. An example of a product development effort in which all the aspects of agility come into play is that of small, portable DNA analyzers. These instruments can be used for analyzing suspected bio-terror agents (e.g., anthrax), performing quick medical diagnoses, or undertaking environmental bacterial analysis. These instruments must be accurate, easy to use, and reliable under wide-ranging conditions, and their development depends on breakthroughs in nanotechnology, genome research, and micro-fluidics. Developing these leading-edge products requires blending flexibility and structure, exploring various new technologies, and creating change for competitors by reducing delivery time. These are not projects that can be managed by traditional, prescriptive project management methodologies. Some people mistakenly assume that agility connotes a lack of structure, but the absence of structure, or stability, generates chaos. Conversely, too much structure generates rigidity. Complexity theory tells us that innovation—creating something new in ways that we cant fully anticipate (an emergent result) occurs most readily at the balance point between chaos and order, between flexibility and stability. Scientists believe that emergence, the creation of novelty from agent interaction, happens most readily at this edge of chaos. The idea of enough structure, but not too much, drives agile managers to continually ask the question, How little structure can I get away with? Too much structure stifles creativity. Too little structure breeds inefficiency. This need to balance at the edge of chaos to foster innovation is one reason process-centric methodologies often fail. They push organizations into over-optimization at the expense of innovation. Agile organizations dont get lost in some gray middle ground; they understand which factors require stabilization and which ones encourage exploration. For example, in a high-change product development environment, rigorous configuration management stabilizes and facilitates flexibility just as a focus on technical excellence stabilizes the development effort. Overview and definitions The Agile Movement in software industry saw the light of day with the Agile Software Development Manifesto4 published by a group of software practitioners and consultants in 2001 (Beck et al. 2001; Cockburn 2002a). The focal values honored by the agilists are presented in the following: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan These central values that the agile community adheres to are: First, the agile movement emphasizes the relationship and communality of software developers and the human role reflected in the contracts, as opposed to institutionalized processes and development tools. In the existing agile practices, this manifests itself in close team relationships, close working environment arrangements, and other procedures boosting team spirit. Second, the vital objective of the software team is to continuously turn out tested working software. New releases are produced at frequent intervals, in some approaches even hourly or daily, but more usually bi-monthly or monthly. The developers are urged to keep the code simple, straightforward, and technically as advanced as possible, thus lessening the documentation burden to an appropriate level. Third, the relationship and cooperation between the developers and the clients is given the preference over strict contracts, although the importance of well drafted contracts does grow at the same pace as the size of the software project. The negotiation process itself should be seen as a means of achieving and maintaining a viable relationship. From a business point of view, agile development is focused on delivering business value immediately as the project starts, thus reducing the risks of non-fulfillment regarding the contract. Fourth, the development group, comprising both software developers and customer representatives, should be well-informed, competent and authorized to consider possible adjustment needs emerging during the development process life-cycle. This means that the participants are prepared to make changes and that also the existing contracts are formed with tools that support and allow these enhancements to be made. According to Highsmith and Cockburn (2001, p. 122), what is new about agile methods is not the practices they use, but their recognition of people as the primary drivers of project success, coupled with an intense focus on effectiveness and maneuverability. This yields a new combination of values and principles that define an agile world view. Boehm (2002) illustrates the spectrum of different planning methods with Figure 1, in which hackers are placed at one end and the so called inch-pebble ironbound contractual approach at the opposite end: Hawrysh and Ruprecht (2000) state that a single methodology can not work for the whole spectrum of different projects, but instead the project management should identify the specific nature of the project at hand and then select the bes