Software company internship report




















Database team 6. Testing team 3. Level 3 - Senior Software Engineer 1. Level 2 -Team lead, Technical lead Yrs. Level 1 - Project Manager Yrs. Scrum is named after the Scrum in rugby, which is a way to restart the game after an accidental infringement. This entry describes the software development part of Scrum.

At that time they needed a development method that had rapid application development and where product requirements could easily be translated into working code.

These principles later became some of the basics of Scrum. Characteristics: Scrum assumes that the software development process is complicated and unpredictable and treats it as a controlled black box instead of a theoretical, fully-defined process. This is one of the biggest differences between Scrum and the Waterfall and Spiral methodologies, which view the software development process as a fully defined process.

Most problems encountered when using these older, formal types of methodologies are: Requirements are not fully understood at the beginning of the process. The process becomes unpredictable when new tools and technologies are used. To manage these processes with flexibility, Scrum supplies techniques and controls to manage this unpredictable process. Development Phase Techniques: Team creation Scrum believes that a development team should perform as a sport team, every team member working independently but towards the same goal.

Scrum suggests that a team has a maximum of 6 - 7 members. The team facilitator is called the Scrum master. The Scrum team as a whole defines the practices, meetings, artifact and terminology of SCRUM for the team and the Scrum Master ensures adherence to these "norms" identified. Scrum masters serve a facilitator role and their authority is mostly indirect.

The master also focuses on ensuring transparency into the development process by maintaining the multiple Scrum artifacts defined elsewhere in this article. Backlog creation There are 3 types of backlogs: Product - Acts as a repository for requirements targeted for release at some point. These are typically high level requirements with high level estimates provided by the product stakeholders.

Release - Requirements pulled from the product backlog and identified and prioritized for an upcoming release. The release backlog contains more details about the requirement and low level estimate which are usually estimated by the team performing the work. By completing, that means fully coded, tested and documented. These are the items that the team will "Burndown" against throughout the duration of the sprint.

Project segmentation The whole project gets divided into periods of time with a maximum duration of 4 weeks. One period is called a Sprint and every team gets a backlog to execute within the given Sprint. Scrum meetings During the sprint, the team conducts daily scrum meetings. The meetings are held in the same place at the same time every work day. The scrum master is responsible for asking every team member the following three questions: 1.

What have you done since the last scrum meeting? What has impeded your work? What do you plan on doing between now and the next scrum meeting? Here a detail of agile is described. Key Features of Agile Software Development: Iterative: Entire application is distributed in incremental units called as iteration.

Development time of each iteration is small couple of weeks , fixed and strictly adhered to. Active Customer involvement: There is lot of client involvement and face-to- face interaction. Every iteration is tested and approved by client. The feedback obtained is implemented in subsequent iterations; thus minimizing risk and ensuring higher client satisfaction. Feature driven: More emphasis is on providing the required features in the application.

Fixed Time: Each iteration has a fixed time span in which it is delivered. Priority based delivery: Features are prioritized depending on customer need, development risk etc. High priority features are developed first. Adaptive: The methodology in general is very adaptive, so that the application that is developed can cater to inflow of new requirements throughout its development.

Empowered Teams: The project teams are generally small and have lot of interaction and communication. People Centric: More emphasis is on using the adequately skilled people to do the development than on following the processes.

Rapid development: Generally the development is done rapidly using light weight development technologies. Simplicity: Emphasis is on keeping things as simple as possible and being open to change.

Why Agile: Benefits to the Customer 1. Customer is more actively involved, and gets higher priority 2. He gets to know regular and frequent status of the application 3.

Requirements are accepted after each iteration 4. Since the methodology emphasizes rapid delivery, time-to-market is less. So the key functionalities can be available to use sooner. Delivery is defined by fixed timescale. So customer is assured of receiving some functionality by a fixed time period. More Testing is done, so better software quality is delivered Benefits to the Project Teams 1.

Project teams are involved more actively in all the stages, have to ask right question. The teams collaboratively take the decisions and are more empowered. Since the development is Incremental, teams can focus on the specific requirements at any given point of time.

More emphasis is on developing the application only, and not on documentation. Simple and minimal documents are used to exchange the views 4. The teams receive frequent feedback as the testing is integrated; so the rework is reduced 5.

Less time is spent in gathering requirements as all the requirements are not gathered upfront and are implemented as and when they arise. So less time is required for planning. Less cost of development as rework, management, documentation and other non- development work related cost is reduced. Teams develop applications collaboratively and in cooperative environment.

It impacts Management more than Developers. Management had to be more open, be actively involved in development process and more importantly allow the teams to take decisions. When to not! Is functionality split-able 2. Is customer available 3.

Are requirements flexible 4. Is it really time -constrained 5. Starts with a kick-off meeting 2. The known requirements are understood and prioritized. The development is plan is drawn accordingly. Relative complexity of each requirement is estimated 4. Sufficient design using simple diagrams is done 5. It can help in avoiding over-coding.

Development is done, sometimes in pairs, with lot of team interaction. Ownership of code is shared when pair programming is done. The code is tested more frequently. Depending on the feedback received, the code is refractor.

Refactoring does not impact the external behavior of the application but the internal structure may be changed to provide better design, maintainability. Some ways of refactoring may be add interface, use super class, move the class etc. Visualization helps development organizations to understand the project schedule and see the scope both of the entire project and of each iteration within the project.

Datasoft management helps teams visualize the available resources to make sure they have the time, money, and personnel to complete the project. Additionally, Mariner helps teams organize iteration or sprint plans to manage and schedule software releases. Datasoft Team also helps teams stay aware of the scope of an agile project by keeping track of user stories within XP, managing project and sprint backlogs within Scrum, or tracking tasks for other methodologies.

These applications can be pre-installed on phones during manufacturing, downloaded by customers from various mobile software distribution platforms, or delivered as web applications using server-side or client-side processing e.

JavaScript to provide an "application-like" experience within a Web browser. At checkout time, the items in the shopping cart will be presented as an order. At that time, more information will be needed to complete the transaction. Usually, the customer will be asked to fill or select a billing address, a shipping address, a shipping option, and payment information such as Paypal, or Cash on Delivery.

An e-mail notification is sent to the customer as soon as the order is placed. Sajawal Shahbaz for the project. We divide our Work in modules. Of course, Our Project Manager Miss Juhinah Batool gave us instructions so that we could understand the project in short time and also assigned me the bugs to be fixed.

Without her helpful mentoring, we could not be involved with the project successfully. Reflective Journal Entries 8. They ask me about area of my Knowledge. Then my test was taken which was actually an Assignment. After completing my 1st task they admit me as an internee. Day by day I received simple tasks that I completed and Present to the supervisor.

I met many peoples there. They Guide me properly and also ask me about some teachers. My Supervisor Ask me About Databases. I present some of old projects including relation database diagrams. They give me a task of making a relational database of School Management System. How to remove dependencies functional dependency vs transitive dependency. How to makes Schemas of related Tables. I add a new project as web form application and start working on it.

It was not designed in 3 tire architecture. I also designed Teacher Portal and Admin Panel. Where teacher can see their Payment dues, Get Pay slip, and Attendance. Before starting this project I was given a proper documentation. I was asking for some revision including style of front page, applying master pages to all, and Make it user friendly and mobile friendly.

We present our work to Supervisor. After checking my work they issue me certificate. Critical Analysis 9. I joined Step Up at an intern to learn and apply my knowledge. So I always had an attitude to be involved more into the project and be beneficial for both myself and the company.

So, from my point of view, I have always been enthusiastic in my work. They were never annoyed to answer even to my stupid questions. And at the same time, I could catch everything that they have been telling me.

I was assigned to the project of course because my team lead found me dependable. Now, I am trying hard to keep this reputation in Step Up. Because, in this 6 weeks I have become a trusted body for my co-workers. They find me to be dependable and rely on me. And I have got many responsibilities towards my project and my co-workers. This expresses my performance at Step Up Under perpetual licensing, software is paid with a big lump sum upfront.

Vendors can realize the revenue immediately and take advantage of the time value it generates for other investments. Since the total cost of ownership is pre-negotiated, customers on the other hand have better control over software budget for the year.

In addition, perpetual licensing is the conventional method, which both vendors and customers are accustomed to. The concept is easier for vendors to explain and for Client to accept. Include ways in which the firm can improve Step UP performance and competitive advantage. Conclusion The internship program helped me to gain important knowledge on the software industry, there culture, work environment and all about software development.

Participating in the weekly team meeting with CTO, Project manager and other team members and discussing the threats of the projects helped me attain the faith to develop a never give up attitude. At the same time, it helped me learn the software life cycle SDLC used in the software industry and inspired me to be striver, responsible and confident. Team discussions like brainstorming sessions helped me identify and solve numerous problem issues which would have been impossible to solve otherwise.

I would like to convey my thanks to the Department of Computer Sciences, UAF for providing me with an opportunity to gain an idea of the competitive environment in the professional field. It has certainly lifted my software development skills in terms of design and coding.

I now look forward to facing the upcoming challenges of the world Annexes Total views 7, On Slideshare 0. From embeds 0. Number of embeds 4. Downloads Shares 0. Comments 0. Likes 5. You just clipped your first slide! Clipping is a handy way to collect important slides you want to go back to later.

Now customize the name of a clipboard to store your clips. Visibility Others can see my Clipboard. Cancel Save. When they are ready to make that vision a reality Kazians work out the details - drawing and re- drawing ideas into real software interfaces. Kazians can produce each and every element of the graphical interface or can collaborate with external design teams to bring disparate elements together to tell a single story. But interaction design is Kazians passion. It is one place Kazians never compromise.

There is only one option for software interfaces: simple. Over the years we have become very good at this art of making the complex simple. Kazians have worked with many technology platforms and have collaborated with many teams over these years. Its clients get a team of their own — it is as simple as that. There is no red tape — the team adapts to the working process of the client and are there as one of their own.

Its integrated quality assurance approach incorporates all aspects of agile and lean development with the stability and reliability of traditional SQA process [5]. It believes software quality assurance is only possible with a mixed set of procedures which should involve all members of the team collaborating with a dedicated SQA professionals. This helps Kaz to provide unique resources bringing in skills, experience and ideas from very different sectors.

It understands this need and helps the customers building up their content. Its research teams have researched, compiled and maintained content in diverse fields and for a variety of applications. The research team is supported by data specialists who leverage technology to optimize data gathering and ensure that the data is stored and managed efficiently.

The data team is also key for services for sifting, extracting and adapting data from various sources and making that usable for the software teams to show within the product. So the employees work in a domestic environment in Kaz. They have a large balcony in each floor which is used for the refreshment of the employees.

Number of employees in each room depends on the size of the room. Since the beginning, Kaz has grown in number of resources and production every year. Kaz doesn't hire developers, designers or QA engineers; Kaz hires people who solve problems. And it hires only the best. Kaz runs regular training and review sessions to keep it on the top.

And the culture of constructive criticism, learning and sharing expands Kaz horizons and keeps it level headed. Kaz has worked with many technology platforms and has collaborated with many teams over these years. Clients get a team of their own — it is as simple as that. It does not specialize in particular technologies, but it has definitely proficient and experienced with a wide array of tools and systems.

Every product is unique and it tries to fit the right team with the right skills for that particular product. Its teams have worked on web applications, created desktop applications and built numerous mobile apps.

Some of those are given below. Motivation factors are important for high productivity. Kaz provides several facilities for the employees.

All the current and ex-employees are members of this Kaz family. Work is fun here. Employees consider the company to be their own responsibility. Also, there is tea, coffee and snacks available all the time.

Also, one of the balconies is equipped with indoor game tools like carom, dart etc. Employees are taken out of the country for anniversary of Kaz every year. I am sure these are only a small fraction of the facilities available at Kaz.

In spite of being an intern, I received all these facilities and consider myself lucky. There is a hour break from pm for lunch and sports. Cultures that I have found in Kaz Software are discussed below: 2. And it hires only the best [7]. It runs regular training and review sessions to keep employee on the top. And its culture of constructive criticism, learning and sharing expands our horizons and keeps employee level headed.

Kazians are very careful to maintain a culture that helps attract talented people and helps them achieve their best performance [7].

This culture starts from work place structure to operating principles of the development teams. From color selection to furniture orientation Kazians have been very careful to create an environment that actively enhances the knowledge exchange and collaborative nature of our work. Kazians are always obsessed with something [7]. People outside of Kaz point these out as signs of our insanity. But Kaz proud of them. Every year in May it has Kaz premier league KPL game and every one goes crazy preparing for the games or buying players or betting on outcomes.

There are huge parties on the final day. This is Crazy but great fun. From color selection to furniture orientation it has been very careful to create an environment that actively enhances the knowledge exchange and collaborative nature of work. They also run various training programs for them to teach them skills that they can use. Figure 5: Helping the Community Being intern, I was not treated as fresher, so I did not have to give a treat to all.

This is the Anniversary Trip of Kaz. Figure 6: Trip to Bangkok My Project Involvement It is maintained by Kaz content team who keep the database up-to-dated. So, the QA team was very active and bugs were being reported. I was assigned to fix some of the given bugs. My involvement was about 2 weeks, after that the project was completed and deployed. Rayhanul Islam BIT for the project. He gave me instructions so that I could understand the project in short time and also assigned me the bugs to be fixed.

Without his helpful mentoring, I could not be involved with the project successfully. He gave me a list of technologies and I learned them.

So this kind use case were failing test and needed to be fixed. So all this paths needed to be considered for the fix. The publisher had a functionality which identified specific keywords in the inputted text in the editor and converting the matched text words to link. There was a bug while finding and converting the matches. Some of the matches could not be matched because of html and text view difference. There were similar issues. So this bug was assigned to me.

I identified the critical cases and used regex to fix them. Bug solving is the best way which provides me the opportunity to familiar with more tools and more Technologies due to spontaneous switching from one project to another. As a result I learn more things from bug solving. And this project was almost a complete project which I needed to understand in a short time all by myself. As I was assigned to fix bugs, I needed to have clear knowledge of the operations inside so that I could figure out the wrong logic there and correct it.

It was a real challenge for me. However I am sharing the technologies I have been working on here. It has 3 sub-parts and each part is being developed in parallel. I have been involved in all 3parts and realized how large an industry web application can be.

Ongoing consideration. I chose this organization because I find their mission to be important and relevant to my career goals. My role at [ Company Name ] was to [ details ]. I worked directly with [ team ] in [ internship responsibilities ]. During my internship experience with [ Company Name ] , I was able to develop my [ skills ].

I particularly found [ experiences ] to be useful in improving my [ skill ]. Although I found [ experience ] to be challenging, I found it to be valuable in developing my [ skill ].

While I had many useful experiences at [ Company Name ] , I feel that I still need to develop my confidence levels with [ task ]. I would have enjoyed more time completing [ task ]. In conclusion, [ details ]. Related: Intern Resume Examples.

While there are many formats you might choose for your internship report, here is an example with the above template:. Jessi Jones School Counseling Internship. Rogers Middle School. Rogers Middle School was founded in to educate the children of Dallas.

Rogers Middle School plays a vital role in the community with after-school programs and weekend tutoring events. I chose to complete my internship with this school because I enjoy the work they do with inner-city children through outreach efforts and after-school educational programs. My role at Rogers Middle School was to evaluate the counseling program and work with middle schoolers. During my internship experience with Rogers Middle School, I was able to develop my active listening, planning and treatment plan skills.

I particularly found direct interactions with these middle school children to be useful in improving my counseling skills.



0コメント

  • 1000 / 1000