Lecture 26 - Software Development Methodologies

Figure 1: Software Development Methodologies

"Walking on water and developing software from a specification are easy if both are frozen".

Software development methodologies are promoted as a means of improving the management and control of the software development process, structuring and simplifying the process, and standardizing the development process and product by specifying activities to be done and techniques to be used. Methodologies aim to place a degree of control over a software project, enabling it to be steered toward a successful conclusion through a proven series of steps and actions. It is often tacitly assumed that the use of a software development methodology will improve system development productivity and quality. A successful software development methodology defines how all of our tools, techniques, and practices combine into a winning formula.

Learning from class:

Today the lecture conducted by Ms. Manisha Peiris. Lecturer started off the lecture by stating that Methodology were not for the systems since there is no any methodology specialized on CRM development, MIS development or PPS development but methodologies were design to cater more projects. 

Then lecturer discussed what a methodology Is. According lecturer its a framework that used structure, plan and controlling the process of developing an Information System. In software development main goal is to make sure output that produce should have quality. If the final product in low quality client definitely will not satisfy with the product and they will simply reject the product. To overcome above consequences development teams needs to organize their work appropriately. In as general to over come above problems people studied this software development process and realized even though software differs from company to company from user to user or context to context but when looked into process of development there are common things that applies to every project such a plan, gather requirements, design the system, developing and testing. Basically the software development methodology is an arrangement of common steps to follow in order to make sure the output is quality and best align to client needs.

After that lecturer stated all the methodologies that people identified were not accurate. As example in Chaos Report the success rate of software development project is just below 20% that means more than 80% projects were fail to accommodate the project in Budget, Schedule and the Degree that met the requirements. The bottom line is that people need to come up with a way that try to reduce the impact on those areas. This is where methodologies comes into action but just following methodology does not resulting a project success according to Chaos Report almost all the projects were followed some sort of methodology which was not succeed at the end.

Then lecturer stated the methodology that use should be appropriate for the project scope and it should align to project deliverable. The project is define based on various characteristic they are,

• What is up Against
• The uncontrollable Constrains
• Time Limits
• Milestones to Achieve
• Progress to Achieve
• Availability of Resources
• Knowledge
• Skill Availability

Then lecture pointed out that students make a mistake when selecting a methodology for their final year project since students need to define what kind of project that they looking at, what are the constrains and limits that unique to project. After that only they should define a methodology that more align in to overcome those problems or challenges to produce a quality output at the end.

After stating above artifacts lecturer specially noted that Structured Methodology or Structured Techniques are not Structured Methods. 

Structured Methods/Tools/Diagrams - DFDs, ERDs, ELH and State Chart (To analyze a problem)

Structured Methodology - The phases of methodology are structured. Example:- SDLC (Systems development life cycle). Ideally SDLC contains a Planing Stage, Feasibility Study, Analysis, Design, Implementation and Operations, Support, Security and Maintenance. Every single Methodology is based on SDLC because SDLC one of the rare or the only methodology which covers the entire spectrum of software development process. This act as basic more or less act as a guide for other development methodologies.

SSADM Methodology -  An old methodology. Focus more on the client requirements that meaning its consider more on the analysis. SSADM does not focus on planing at all. Giving more weight on the Feasibility analysis and design. 

SSADM Phases are,

• Feasibility Study - Try to assists whether the project is practical. There certain tools to assists feasibility not just focus on the Technical feasibility, Schedule feasibility and Economical feasibility. First define the scope and evaluates. Can the solution actually solve the problem and look at the domain of the problem. Can it solve by using IT system.       
• Requirements Analysis - Conduct a very thorough analysis. Look at what the problem is and what are client requirements and focus on every single user of the system basically what they expect.
• Requirements Specification - 

       Functional Requirements - Is a requirement of the system which must be implemented if the functionality is not their the proposed system not solving the problem. Helping students to achieve the objectives of the project.

        Non-Functional Requirements - Functions that deals with the quality of the software system. If these functions contains in the system its better if its not there that doesn't mean the system is a complete failure its just an improvement to the system. This functions rangers to usability, security, backup and recovery. The non-functional requirements define based on the each system specifications.                

• Logical Systems Specification - Basically defines the logic of the solution. How the functional requirements logical been implemented in the system. This used methods of mapping the Data Flows and Behavior of the data.

• Physical Design - Describes the infrastructure basically the hardware required to implement the system. As examples network diagram, physical interface layout.   

The problem in this methodology is that it doesn't mention how to test the system, how to implement or how to program it and how to deploy it.

This method best suite if the students project's key aspect is to analyze and design the solution (conceptuality of the design/solution). But students need to be more critical because this methods owns lot of weaknesses since it doesn't cover some aspects. Due to above consequences students can use this methodology by aligning with another methodology which covers the other aspects of project development process.

Main Techniques/Methods used in SSADM
  

Logical Data Modeling -  Describers how the Data logically retain. For this can be used an ERD to normalization.

Data Flow Modeling - Describes the data flows in the system. For this normally used an DFD.

Entity Behavioral Model - Identify entities that store data and map it with events in DFD when manipulate data in Data Stores. All three together give developer an idea how data should handle within the system. Use an ELH (Entity Life History Diagram)

And Lecturer stated that SSADM starts with DFDs, Context Diagrams and first need to logically map the flow of data in current system as well as based on that improve and map DFDs to the proposed solution.

RUP (Rational Unified Process) Methodology

RUP consist of 4 main phases. They are,

• Inception
• Elaboration
• Construction
• Transition

According to lecturer this Methodology is made for UML because people realized that UML has certain benefits since UML diagrams allows to do quite a good analysis and the requirements are nicely mapped out that enable developer to produce system that more align to customer requirements.

Then lecture told that hidden side of the RUP is all the activities are happening in form as stated below although there are phases these activities happens across the phases. Those activities/disciplines are,

• Business Rule Modeling
• Requirements
• Analysis Design
• Implementation
• Test
• Deployment
• Configuration and Change Management
• Project Management
• Environmental Analysis 

All those activities need to happen in the software development process. 

Figure 2: RUP Diagram

As shown in Figure 2 those activities are like heat packs that represent at what point that activity most significant and what phases those activities not performed at all. According to above diagram there were to iterations under Elaboration (Elab#1 and Elab#2). Elaborations happens basically in prototyping.

Then lecturer stated that there are two types of prototyping, They are,

• Evolutionary Prototyping - Where prototype evolve to the final product

• Throwaway Prototyping - Prototype is build just for the sake of getting requirements right and get approval. Final version build on scratch.

Then lecturer highlighted that Prototyping used to be an methodology but now its just an tool. All the methodologies currently available used prototyping as an activity within it.

Agile Methodology

According to lecturer Agile is not a Methodology its just an guideline. There are 16 guidelines available and all those guidelines talked about the usage of this concept agile in software development process there are certain things to have infuse into it. The Agile consortium states that individuals and interactions over processors and tools. Basically its says don't restrict or constrain the project to processors and tools that need to perform focus more on the people or team and the interaction between them that result in better development. Working software over comprehensive documentation. The bottom line is that Agile Alliance feels that the output should be more focus since its the product that client actually get and client assess the success of the project based on what they sees. Because of that no point of focusing more on documentation. Beside above sequences there are other aspects such as,

Customer collaboration over contract negotiation - This is commonly done where the Software development team get requirements and sign off. Develop only client sign off. Agile eliminating this aspect by enhancing the customer involvement and make sure the output product meet the requirement  when the product implementing.

Responding to change over following a plan - Most project development teams come up with a project plan and stick to it. But Agile says response to changes in in more priority rather than ignoring it.

Then lecturer said that Agile manifesto is really long since it contains many rules to follow. Some of the main points are,

• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes harness change forth customer's competitive advantage.

Then Lecturer noted those rules more or less believes since doesn't tell what to do it and when to do it.

After that lecturer driven the lecture into by explaining some Agile Methodologies.

SCRUM Methodology:

              

SCRUM is Methodology that originated from the concept in Rugby. The concept that taken from rugby is the fact that it needs lot of team effort involvement and this SCRUM methodology design around that. The fact that if project team needs to produce a good output, the entire team need to be close net or have to work together. In SCRUM there are waggly define phases but it talks about certain essential rules that needs to within the project along with some tools.

Figure 3: SCRUM Methodology

               

According lecture as shown in above diagram it describes that ones the project team started off gathering requirements they develop a Product Backlog basically requirements which as been assess and prioritize. After that Product Backlog transfer in to Sprint Backlog. Sprint is basically an iteration where one iteration takes 2 to 4 weeks and there is timeline. The backlog break it down to manageable components. Basically transfer backlog into to smaller sprints and go through a sprint. Then lecturer noted that every 24 hours there is an SCRUM meeting which held by Scrum Master. The Scrum Masters responsibility is to make sure is there any project progress, Identify challengers, Make sure those challengers are overcome. Ones the above processes done project team go into developing the system, testing and deploying.

DSDM Methodology:

Lecturer stated that DSDM is a heavy methodology because it more specific compare to the other Agile methodologies like XP or Cristal since those are very wage since those methodologies doesn't exactly explain what phases to carry out. The specialty of DSDM is it does that.

Figure 4: DSDM Methodology

Lecturer discussed the DSDM phases by using Figure 4 diagram. As stated by lecturer it starts off with sequential manner. Basically it needs to do a Feasibility Study after that to have a very good understanding about the Business Study. After that it goes in sequence of iterations. In those iterations there are sub phases/tasks as shown in Figure 4. The specialty of this methodology is at any time can go back and can do necessary changes. Theses processes repeats until the client happy with and till the software align to its identified specifications. This entire methodology is a big iteration.

Before concluding lecture for the day lecturer stated before selecting a methodology there are certain things to consider.

What to Consider?

• Scope - What are the things that planning to do in a project. Check whether there is sufficient time. Arrange the phases in a way that can do in parallel or iteration to maximize the time.
• Deliverable - What need to be output according to client requirements. And those deliverable needs to be align with a methodology where it can facilitate that.
• Constrains - Requirement gathering level and probability to identifying them.
• User Involvement - Enable users to interact with the project team in certain points in order to get their feedback and review on the progress.
• Nature of the Project - What kind of a project is focus on. Identify the things to in order to complete the project successfully.

Reality of the Lecture:

From this lecture I understood that there are various methodologies available to align with project process. How ever some methodologies does not suits for every project. Selecting a proper methodology is really important since it results in failure or the success of the project. If the project need to consider more on the client requirements since requirements unable to identify at a stretch methodological such as SSADM can be use. In order to have better analysis and software development process methodologies like RUP can be used in large projects since it deliver well balanced phases. Agile Methodologies such as SCRUM and DSDM comes into action since in the real world project requirements were dynamically changes from time to time during project process. To deliver timely applicable project to client by overcoming and replying requirement changes project teams prefer Agile Methodologies since there is great flexibility and freedom by using them. After considering above consequences I gain a better knowledge on Software Development Methodologies than I had previously as well as this lecture enabled me to structure the theory content of the methodologies in a way that enables me to apply them depend on the project scope been selected for my final year project. I'm sure further research on these Methodologies will enable me to gain an Industrial level knowledge that will help me to perform tasks smoothly in my future career.

Industrial Visit to Virtusa

Company Profile:

Figure 1: Virtusa Logo

Virtusa Corporation is a global information technology (IT) services company providing IT consulting, technology and outsourcing services. Global 2000 companies and the leading software vendors in Communications & Technology, Banking & Financial Services, Insurance, Telecommunications, and Media, Information & Entertainment industries. They build and sustain application platforms for their clients that create competitive advantage. Founded in 1996 and headquartered in Massachusetts, beside that they operates offices and technology centers throughout the United States, Europe and Asia.

Company Introduction and its Framework:

After visiting to the company in Virtusa New Building Auditorium, students had a brief introduction from graduated students who are currently employe in Virtusa and they explained About the company, working experience and the positive outcomes that gained after engaging with this company.

Figure 2: Mr. Shehan Warusavithana

Then after friendly discussion with them, the program headed by Mr. Shehan Warusavithana that shown in Figure 2 who is currently the director in technology at Virtusa. At the stating point of the presentation Mr. Shehan mentioned that he joined as a software architect in 2003 to Virtusa and before that he worked as a software consultant for JP Morgan Chase (US) during 2003 - 2007 (4 years). During that time he was part of the team that built the largest online banking system in the world which received him the ultimate industrial experience that ever can expose during the career. Then Mr. Shehan driven the discussion back to the company and stated below artifacts,

About Virtusa:

• US company - Headquarters -Westborough, Massachusetts, USA
• Offices -Throughout US, Europe and Asia 
• Technology Centers -US, UK, Hungary, India and Sri Lanka
• Number of Professionals - Over 5840
• 89 active clients that give significant amount of business; almost millions of dollars.
• Listed on NASDAQ (VRTU) - US Stock Market
• Revenue for the year 2012 is $277.8 and for this year (2012) $330 million is being expected.
• The revenue target for the year 2015 is $500 million and for the year 2018 is $1 billion. These targets are achievable because Virtusa has the skills and professional that they can actually deliver those targets.

Value Proposition:

 

To show innovation, creativity and efficiency into the work done and save money in the process.

Customers:

• Financial : Standard Chartered, Pay Pal, New York Life, Cardiff, JP Morgan Chase & Co.
• Media and Communication: Cisco Systems, Qwest.
• Technology: Harte Hanks Trilluum Software, HC Pro, Datacert, Pego.
• Media: Thomson Reuters, Iron Mountain, National Gepgraphic.

Awards & Recognition:

• HRM gold award - Corporate Research Foundation (CRF) Institute
• Boston Globe Award - Virtusa was ranked 42 in The Boston Globe’s Globe 100 List
• Forbes' list of the "100 Best Small Public Companies in America.

Corporate Social Responsibility (CSR) Activities:  

Virtusa's Corporate Social Responsibly programme is embodied in three key initiatives. They are,

• Digital Research Initiative - Set up an information system IT labs in rural areas.
• Campus Reach Initiative - Provided 21000 campus training.
• Code Green
• Supported National Integration - Rehabilitation of ex-LTTE combatants.

Domain Expertise:

• Sectors that Virtusa mostly cater and generate revenues
• Telecom: 30% revenue
  Banking and Financial: 58% - 60% revenue
• Insurance
• Healthcare - Sated as the recently growing sector
• Media and Entertainment

Main Projects done by Virtusa:

• Telecom Fault Management System for British Telecom
• E-Gateway for ICTA
• Tracking life cycle of aircraft components for Pratt & Whitney by using .net.
• Cheque scanning and depositing system for JP Morgan Chase & Co.

Ongoing Major Projects:

• A fall tracker for patients and old-aged people for Philips Montreal Project

Companies Training Programs:

• On boarding
• Personal engineering excellence
• Technical skills
• Soft skills
• Team Building

Knowledge Management and Collaboration:

Maintaining a portal like Social Media

     -Yommer

     -Vingo

     -vT

     -vTube

Compensation and Benefits:

• Basic salary
• Motor car allowance
• Quarterly bonus
• Facilities like Dinner, Transport after hours, Gym, Pool tables.

Figure 3: Mr. Shiham Nawaz

After that the discussion handed over to Mr. Shiham Nawaz shown in Figure 3 discuss about BPM practice done at Virtusa.

Mr. Shiham started his presentation by stating that BPM stands for Business Process Management and can be defined as an umbrella term that describes the methodologies, metrics, processes and systems used to monitor as well as to manage an enterprise's business performance.

Figure 4: Basic Project Management Triangle

Mr.Shiham then explained that BPM revolves around engineers in the business process by participating Business Analysts, Architects, Managers. There is a high demand for Engineers from all the aspects in BPM since many companies moving their tradition business process to automation as well as Harding and enhancing the current system in order to cater ever growing business needs. BPM engineers need to have a basic knowledge about other BPM processors since they work as team to deliver the end product what client acquired for. Beside that Mr.Shiham noted for BIT students they can start their career path through Business Analyst where the role's main responsibility is to act as the interface between client and the programmers basically to identify the customer needs and arrange necessities in a way that convenient to programmers. The main objective of BPM is to business process re-engineering basically automating the process involves to reduce the cost and time as well as enhancing the quality. This made possible since Virtusa currently dealing with 5th generation languages ex:- Pega Platform.

BPM adds Value to the followings:

• Adds Value to Customer
• Adds Value to Customer's Customer
• Adds Value to Employees

How BPM supports to Project Team:

• Separates business logic from technical aspects
• Exposes another layer for business functionalities
• Brings business domain knowledge by analyzing and modelling
• Brings technology knowledge by architecture and design

Virtusa evaluate it performance through Time, Cost, Quality, Customer orientation, Employee orientation and through Work Culture of the organization.

Before concluding the BPM session, Mr.Shiham stated that BPM practice employs close to 10% of the total Virtusa headcount and its revenues contributes to 25% of the total organizational revenue. Currently Virtusa serves to 31 accounts and nearly 100 individual clients that widespread globally who retain and continuously acquire for company's services.

After that students headed to discussion board room in the intention to expose students to real working environment basically to observe how project steps were executed within Virtusa. Students were exposed to a project that Virusa currently working on named as Philips Montreal. The main purpose of this project is to develop a fall tracking software to the Philips that enables them to track and provide further services in a blinking eye by linkage with medical service to subscribed old aged people when they met with accidents.

Students were addressed by members of the project team and they started off by briefing the project scope. According to them this project is done for the healthcare domain of Philips. The reason why Virtusa received this project is because Virtusa has already completed many Philips project successfully because of that they gained strong client relationship and they pioneer in proving services for healthcare domain.

Figure 5: Philips Montreal Project Team (Virtusa)

Then the Project team shown in Figure 5 explained their main requirement gathering method as Workshops (Hot Houses). Hot Houses means where development company and the Client book an official place for some days to interact with each other on purpose to gather requirements from the client's representatives directly. Since this process involves many arguments and discussions it named as "Hot House". The main advantage of a Hot House is, it enables development company to identify and gather necessary requirements within a short period of time than other requirement gathering method.

Then they driven the session to project scheduling, basically the project execution plan. They stated that they used an iterative model as it is easier to get feedback then and there and enables to do change accordingly depending on the clients preferences. Along with above facts they mentioned that they have been used many number of use cases in each stage of the execution plan. As depicted by presentation slide in the first stage they started off with 2 use cases, in the second stage 12 use cases and then in the final stage there were 31 use cases. Although this project completed up to some extent, project team mention its not efficient to keep many use cases at the end stage of a project since there is no way to get client's feedback for them as well as it may results some errors in the final product.         

After explaining about the Philips Montreal Project, Project team stated the development process that involved in any project environment. This list filed up as,

• Architecture Level : Discusses about the Technology, Maintainability, Scalability
• Design Level : Discusses what are the interfaces and software components
• Low Level Design (LLD) : Designing use cases and coup with little coding
• Development: Checking the quality of work done by peer review and lead review
• Quality Assurance
• Tracking Risk issues and Mitigation issues

Before finishing off the session project team stated in order to do projects like Philips Montreal Virtusa use PEGA platform that build on J2EE framework. The real benefit by using above mention platform is it reduces the time taken to complete a project since it enables many professionals in different specified areas to engage on the same project as well as it generates most of the required code for software implementation based on the functions that provided to the platform.

Industrial Visit Outcomes:

Before visiting to the Virtusa I heard that they are the Sri Lanka's Best IT Solution company. They promote their career vacancies through various online websites with attractive banner ad's because of that I was bit aware of the company services before I go there. Some of the news that I heard about the company was not good up to some extend specially on the salary provided for the employees. But I was able to learn the true side of the Virtusa and how its cater to clients by utilizing the employees capabilities by shaping them to organization culture. During the sessions that conducted by various representatives from Virtusa enabled me to learn areas such as new requirement gathering methods as an example "Hot Houses" and the session on BPM open me an area of new phenomenal to study on since business processors engaging with new technologies to coup with ever growing business needs. In the industrial level project were executed in a systematic where every each and every expertise in relevant area can contribute to the project without any interference and to keep the project always on going some team members were send to on shore locations where other members were stayed back off shore since to overcome communication barriers and huge time difference. I understood that the project that we carry out during academic career were totally lies in foundation/basic phase when comparing with industrial level projects that carries out by companies like Virtusa and it deals with many professionals along with their ideas to finally output a client satisfied product since the client stated to be the king and company deals with peoples money not with marks as we get in academic life. I hope my practicality will benefit more on me in industrial level since that my theoretical knowledge will provide me the gateway for it.                    

Lecture 25 - Harvard Citation and Referencing

Figure 1: Copy Paste

"When a thing has been stated, have no scruple. Take it and copy it. Because it your own work".

As stated by Warwick (2011) "From reading academic articles and books, you should be familiar with the scholarly practice of making references in the text to other people's work and providing listings of relevant source material at the end of the text. Why is this done, and why should you adopt this approach in your own work? There are several reasons:

• To enable someone reading the document to find the material you have referred to or consulted;
• To demonstrate your width of reading and knowledge about a subject;
• To support and/or develop points made in the text;
• To avoid accusations of plagiarism: using somebody else's work without acknowledging the fact".

Learning from class:

Lecturer started the lecture by stating that students need to do references in their academic projects according Harvard Reference format as well as need to align reference methods in proper way.

Then lecturer discussed that citation should always be within a full stop. As an example: ...... Services (Jeodth, 2012). And the citation is apply for a one sentence basically from one full stop to another full stop.

If students need to refer big chunk of paragraph or text then students need to exclude first 1 and 1/2 half lines and last 1 and 1/2 half lines of the paragraph where the other content need to be indented. As an example:

Then lecturer stated above type of citation styles seen only in literature type of documents where people need to quote basically for direct quoting. As students literature type of writing can be found in critical evaluations of literature documentations. 

The reference is used to acknowledge some ones pieces of work and the validity of a citation is valid from stating point until it reach a full stop. Apart from that other content is considered as authors work. According the lectures experience most of the students normally reference the content but there no citations align to it. If there is reference its a must to have at least one citation in the document and if there are multiple citations for same particular statement because of the same idea stated in different sources, students need to put multiple citations as Johan 2010; Peter 2012; Deme 2011. The citations were not count as part of the total word count of the document. In Microsoft Word, Word Plugging enable students to do reference and citations where it allows to generate document word count without any citations.

Then lecturer discussed How to use citations at the beginning of sentence

This applicable when the resource authors name naturally occurs in the sentence the citation (Surname of the author) appears out side the citation and the inside the citation contains only the year and page number. Bellow is list of examples on various formats of citations where it can used at beginning. They are,

• As stated by ABC (2012)

• According to ABC (2012)

• As per ABC (2012)

• As said by ABC (2012)

• As mentioned by ABC (2012)

• As told by ABC (2012)

• As reflected by ABC (2012)

• As depict by ABC (2012)

• Based on ABC (2012)

• As pointed out by ABC (2012)

• In companion to ABC (2012)

• ABC (2012) describes that

• Based on the  investigation ABC (2012)

• As proved by ABC (2012)

• As said by ABC (2012)

• ABC (2012) agreed that

• ABC (2012) makes the point that

• ABC (2012) says that

• As criticized by ABC (2012)

• In comparison to ABC (2012)

• As ABC (2012) wrote that

• As noted by ABC (2012)

• ABC (2012) argued that

As students its better to have a mixture citation patterns which reflects the students knowledge in language.

Before concluding the lecture for the the day, lecturer stated some Golden Rules relating Citations and References that need to follow when working on a Documentation. They are,

1. Don't always stick to one particular frame to introduce references. Better to have a variety or mixture of them.

2. Don not quote (Copy Paste). If its direct copying use inverted commas also do not copy pate (quote) more than three lines.

3. Always Paraphrase. State multiple citations. As an example:

• If student cant find the year it should state as "n.b"

4. Try to avoid anonymous author. If its a site state the site name or the organization name that site belongs to.

5. If the year is not available based on the reference content try to find the year. In this case it use "circa" basically state an approximate year for the content. Example :- As Peter stated (2012 C)

6. Citing Interviews/Emails - Have to mention as personal communication by including as "Pers.comm". This need to mention after the name of the interviewed person. As an example (Jame, L.E, 2012, pers.comm., 12 May) 

7. If there is a word to word copy it should placed within the inverted commons.

Reality of the Lecture:             

From this lecture I gained a vast amount of knowledge relating various aspects of Harvard Citation and Referencing which I totally misinterpreted before. Most of the time I have used only few combination of citation mix in my past academic documentations. Today only I got to now that there are various form of citations patterns available to present that will results more interest to the readers. Citation need to be done where it possible for each statement if I reflects another authors statement or an idea. There is no limitation for citations in the document since more you show them the more you have the knowledge that easy results in to develop relevant and more interested content in the document. By adopting Golden Rules relating to Citations and References where it applicable fulfills the academic documentation requirement in more professional way. I hope to use above all the consequences in my future documentations to deliver more standard documentation relating to Harvard Citation and Referencing guideline.   

Reference:

 Warwick. (2011). Why reference?. [Online]. Available at: http://www2.warwick.ac.uk/services/library/help/guidespublications/bib_cit/ [Accessed 4th September 2012] 

Lecture 24 - Project Management

Figure 1: Project Management

No matter how good the team or how efficient the methodology, if we’re not solving the right problem, the project fails  

Project management is the way of managing change. Everything from the Olympics to organizing a wedding can be considered a project where it has a beginning and an end. It describes the activities that meet specific objectives and can be used to introduce or improve new or existing products and services.

Learning from class:

Lecturer started off the lecture by stating what is a project. According to his definition basically a project is a work that done by stick in to a particular time frame, budget to heading towards to achieve a particular goal. The highlighted words sated in the above statement known to be characteristics in a project.

Then lecturer discussed different stages in a project, They are

• Initiation - Define the type and the theme of the project. Examples: Propose the budget required, Date and Venue
• Planning - Breakdown the project into smaller tasks. As an example in a party scenario identify sponsors, print tickets, sell tickets, Decorations, Find a place and booking the location, Assign people for certain responsibilities and divide the budget.
• Controlling - Manage the work been done and make sure the work been carry on according to plan, budget and time frame. Make sure there is no deviation in the plan. Enable to accommodate new actions to be performed by managing the tasks in the plan.
• Complete - Check whether the expected outcome has been achieved within the time as well aligning to the budget

Then lecturer stated biggest reason to failure of projects is because of improper identification of client requirements that happens preliminary stage of the project process and most of the time when new requirements come it unable to accommodate within the time frame which results in not satisfying customer needs. To eliminate above artifacts negotiation helps to create win-win situation for both parties. Strategies like BATNA can be applicable for those scenarios.

After that lecturer stated that it needs provide client expected requirements and the budget need to be alter in favorable way.

Then lecturer stated that project management is basically the way how a particular person manage the project based on the four pillars (principles) in project management. They are,

• Planing
• Organizing
• Leading
• Controlling

                 in order to make sure that the project is completed within the timeline and within the budget.

Then lecturer moved the topic in to project scope and feasibility.

Scope: Defines what a particular person going to do in the project. When new requirements coming to the project the scope should be expanded. The scope also gives an indication of what the person trying to achieve from the project basically the deliverable of the project along with boundaries.

Feasibility: Check whether the project is worthwhile to persuade. There are four feasibility dimensions. They are,

• Technical Feasibility - Available resources and expertise knowledge

• Operational Feasibility - Will the project solve the business problem and how it impacts to the organization

• Economic Feasibility - Study of cost and benefits. Identify return get. Cost can be classified as Tangible cost and Intangible cost and check whether there is a ROI (Return on Investment). Different ways of doing cost benefit analysis are payback analysis, ROI (Return on Investment), NVP (Net Percent Value), IRR, Benefits cost Ratio and ARR.       

• Schedule Feasibility - To check whether the project can be completed within the given time.

Bedside above feasibility methods in certain projects mostly in government related projects they check for,

Social Feasibility which defines whether the people accept the project and use it.

Then lecture stated how to Defines Aims/Objectives

What ever the objectives were identified should align to SMART (Specific, Measurable, Achievable, Realistic and Timely)

After stating above fact lecturer stated what is a Methodology is and why need to use such Methodology.

According to him,

Methodology - People can conduct a project without using methodologies but if there is a methodology in place it helps to achieve the goals been specified and to address the problem more effectively by eliminating potential problem since the methodologies were design address problems.

Then lecturer focused more deeply on project management and stated project management is discipline of planing, organizing, managing and controlling that defines the four pillars of management and controlling resources to achieve the project goal within the time specified period as well as align to budget.

Lecturer also stated that Aims referred to complete the project on time, within budget, with required functionality and quality.

According to above statement quality identity how far particular persons tried to achieve clients expectations by balancing out time and cost.

As for the last section for today's lecture, lecturer stated How to Manage the Project. Specified by lecturer,

• Work to series of check points - Milestones to check for the quality of the work by showing to a supervisor. Basically Quality Assurance the project in certain intervals.
• Control the project by utilizing software -  Can use Case tools (Computer added software engineering tools such as Microsoft Project, Visio and Rational rose)
• Ensures projects scheduled at earliest possible date, with least drain on resources - Make sure the project finish on time and human resources should use in it maximum potential as well as make sure human resources are not over utilize or under utilize.
• Delays identified and increase resources- Identify the risk and their types. Identify the consequences to take if their is a risk. Identify Mitigation strategies (What are the action take place after the problem occurs).
• Adopt a methodology - To face and overcome problems occurs

Reality of the Lecture:

From this lecture I understood that project management enables me to properly coordinate the project task and to gain positive outcomes by overcoming negative consequences. So far for my individual and group projects I didn't use a proper timeline because of that I experienced huge workload to be done on certain days during the work process and I think most of my past projects were successful because content were reviewed by a third party almost all the time that result me to change errors been made during the project work. After learning Project Management consequences I understood that there are other various aspects to be consider on projects specially on industrial level projects to successfully complete according to the given time frame and budget along with customer expected requirements. To facilitate all the above needs I need to come with a better customized foundation for each project that need to be executed and monitor during the time of project's start to end.   

Lecture 23 - Interview Preparation and Procedures

Figure 1: Job Interview

"The best interviews, like the best biographies, should sing the strangeness and variety of the human race." 

The biggest mistake in interviewing is not being fully prepared. It behooves job seekers to use every conceivable means possible to prepare for the interview and to allow ample time to fully prepare. Understand that interviewing is a skill; as with all skills, preparation and practice enhance the quality of that skill. Preparation can make the difference between getting an offer and getting rejected.

 

Learning from class:

Lecturer started off the lecture by stating that interviewee needs to preparer some potential questions that might ask in the interview which enable interviewee to familiar with structure of the answers that planing to provide.

After that lecturer stated that interviewee needs to prepare list of questions along with answers for them, that consist of questions and answers along with consequence such as,

1. What sort of TV programs you Watch?

• Avoid TV series and watching documentary programs that play in Discovery  and History Channel

2.  What are your Weaknesses?

• Mention only one weakness and provide a weakness that also can be seen as a strength. Examples:- Perfectionist, Inability to say No and Not giving Quick Response for highly critical tasks since its requires detailed analysis.

3. What are your Strengths?

• Always need to justify each point by giving examples. As an example if chose Leadership skills provide an example where you demonstrated it and state the outcome of it.

4. Why you need this job?

• Should come up with list of reasons and better to give three reasons and those reasons should highlights motivation and enthusiasm for that particular job. As an example state like "That I have more to offer to the organization and I think it reciprocal I have more things to get from the organization in terms of experience and skills"  
• Need to highlight interviewee dedication and motivation towards the company
•  Highlight the unique projects that company do and how the interviewee can support them 

5.  Why are you good candidate for this job?

• Find three reasons from the quick match sheet that highlight most suitability or best match qualification for the applied job.

6. What do you think or know about our organizations?

• Highlight the uniqueness and finical status of the organization as well as how it differ from its competitors

After specify above general interview questions lecturer stated in interviews there might be tricky questions shoots to interviewee after satisfy up to some extent with general question session. Those tricky questions are,

1. How much of salary you are expecting?

• A good answer would be "This job normally pays in range of  30 000 to 50 000 and I would prefer some upper bound salary"

2. What is your Ambition?

• Ambition should align with the line of work in that particular line or in job area. As example in Business Analysis or Developer the ambition should be a project manager.

3. What if kind of questions?

• These types of questions ask to check How good you are in problem solving. Basically given a mockup scenario or pseudo code to react open or provide the answer.

4. What type of dreams you see?

• Tell about some positive dreams you had.

Then lecturer mentioned that after come up with answers for the above questions candidate should practice those answers in front of a mirror with little bit of expression in face along with good body language movements relating to the answers been provided since the rehashing is the key to success. The more you practice the more you become comfortable.

Lecturer also stated that end of the interview before leaving, it a must to shake hand interviewer since it reflects your professionalism.

Before concluding the lecture for the day lecturer stated there are some Golden Rules to consider. They are,

• Always listen to the question completely and address it
• Always provide evidence what is stated and make sure it referenced in the CV
• Don't Rumble 
• Avoid slang words  

Reality of the Lecture:

From this lecture I understood how well I need to prepare for an interview and potential questions that interviewers might ask in a interview as well as how to structure the answers in a professional manner that outcome a better chance of getting me selected from an interview. The most of the artifacts that learned from this lecture can be define as commons sense that a particular candidate should develop before facing to an interview. I think I clearly grabbed the theoretical aspect of this interview code of conduct and I will use it for my future career requirements by mixing my own flavor of doing things in order to differentiate by self from other candidates.

Lecture 22 - Interview Skills

Figure 1: Interview

Get comfortable. Forget that you in an interview. Say what comes to the Mind.

When people are fed up, need a new challenge, want more money, want a more conducive work environment they start reading the want ads, polishing their CVs, pounding the pavements and trawling for jobs. The current situation, however, does tend to mean that a whole lot of other people are also looking for new jobs, so you need to have a jump on the competition by presenting yourself at interview in the best possible light, no matter whether you've been made redundant or are looking for something fresh and motivating. 

Learning from class:

 

Lecturer started off the lecturer by specifying why there is a requirement for an interview. According to lecturer main objectives were to identify candidates communication skills, practicality, appearance, energetic/enthusiastic level towards its organization.

Then Lecturer stated that there are few types of Interviews. They are

• One-to-One -  Consist of one interviewer (potential supervisor) and interviewee

• Two People - Consist of two interviewers. Normally questions were asked by one interviewer and both interviewers assets the interviewee. Both interviewers assessment will be consolidated regarding the interviewee at the end of the interview.  Normally interviewees address only to one person this is a big mistake that done by many interviewees. Should be address to both interviewers.  

• Panel (Conference) - Every interviewers in the panel assessing the interviewee. In some point every interviewer communicate with the interviewee. As from interviewee side they must challenge to convince each interviewer in to some extend. The success level of convince can be identify by interviewer's reaction such as from a smile since it reflects the sign of approval.

• Group Interview - Select few candidates, call them for an informal Question and Answer session. In the Q&A session all the candidates were short listed and allow candidates to ask question from interviewers. As from interviewees side they must ask really good and relevant questions from interviewers since they assets interviewees based on the questions that they ask. Basically the success dependents on the questions that candidate ask. Should ask questions that reflects the candidate's interest towards the job.   

Then lecturer stated besides the above types of  based on how the interview is conducted it can be further classified as, 

   

• General Interviews (Informal) - Normal discussion between interviewer and interviewee. Interviewer does not well prepared for the interview but there is some objectives to accomplish. Some questions were made depend on the scenario.

• Chronological Interviews - Based on the life events interviewer conduct the interview. Interviewer try to picture interviewee based on the artifacts that they gain from questions. Seek for the logical of career changes and address gaps in the interviewees life. 

• Criteria based Interview - Seeking for evidence whether the candidate fulfill criteria or requirements that specified in job advertisement. This can be achieve easily through by Quick Match Template that provided by the lecturer that enables candidates to well prepare for expectations of job requirements.

Then lecturer described about the Quick Match Template. According to lecturer this allows the candidate to prepare well before facing to an interview or making the CV. First Candidate need to list down what are the qualification,experience and technical knowledge that the company asking for and then need to specify what are the consequence that ccandidate owns to fulfill each requirement of it. This should considered to be number one priority before apply for job since this outcomes facts to make custom made CV for the applicant.

• Technical of Creative Interview - This type of interviews quiz interviewees Technical knowledge

• Telephone Interviews - This conduct over the phone. Enable interviewers to short list candidates. This saves interviewers time since it enables the interviewer to get to know the communication skills of the candidate and enthusiastic towards the applied job vacancy. 

Then lecturer stated how to prepare for a Telephone Interview. They are,

• Need to check for the availability
• Check for a suitable place without any disturbances
• Better dress up formal
• Sit in a proper place without like relaxing on a bed etc.
• Prepare the documents and keep it in a way that easy to use.
• Interviewee can make a good impression by the way they answer to the questions that directed from them.

Then the lecture discussed what to consider before confirming and to face to an interview.

• Check the availability

• Confirm the candidate attendance. Ask the place, time, whom going to meet
  and required documents to bring

• Try to go little bit earlier

• Make a good first impression

There can be instances a person will get two interviews at the same time. If a person face such problem there are two options that candidate can do. 

• Inform one of the companies that called for the interview that by specifying that candidate have another interview and unable to make it. This depict in some ways that the company get to know that candidate have some demand form other companies as well.

• Let the company know that candidate unable to make it due to unavoidable circumstances and ask for another date and time if available. This depict that candidate owns some enthusiasm for the job.

Then Lecturer mention that candidate can be successful in an interview based on mainly three things. How good the impression is made followed by the type of answers that candidate give for the questions that shoots from interviewer. And both above factors possible if the candidate know their capabilities and how to utilize it.

Before concluding lecture, lecture spoke about consequences of better background preparation for an interview.

Background preparation for an Interview:

• Check for the organization profile

• Talk to some people who are currently working to the company. From that can get to know procedures of the company and will helpful to prepare for the interview.

• Try to do a Google search in order to aware of the changes that organization has done, new owner etc.

• Try to read annual reports of the company and find out what kind of issues/problems company has etc.

• Analyze the job - How to fulfill the requirements, do a quick match.

• Need to come up with potential questions that will be asked in the interview and prepared with answers for the questions.

As final word for the today's lecture, lecturer said more the level of preparation for an interview, applicant will get more chance of been selected for an job.    

Reality of the Lecture:

From this lecture I was able to gain different aspects of Interview and the background which related to it. According my understandability main outcome is of the interview is to mirror or picture the knowledge, qualification and experience that a particular applicant owns to its interviewer. In order to accomplish that objective applicant can focus into the main dimensions of interview as discussed in today lecture by fine tuning unwanted information will heading to make a good impression in interviewers mind. In my perspective this enables me to confidently face to any interview since I know the factors to be consider and focus on before go into an interview as well as to get through successfully from the challenge.