Designing a consulting services architecture model

textDuring my years of experience in the technology industry, it has become obvious that standard processes and methodologies within the engineering discipline are at a mature state. The realization though is that software engineering specifically lags behind. Most software engineering methodologies that I have studied focus on the mission of software development. It is this realization and the need for structure that led me to review existing methodologies used within my company's software services organization. The definition of what a successful software services methodology entails is rather limited. This report will provide a history of existing software engineering methodologies that I have studied, describe an initial services method that was being developed within my organization, develop a new model that addresses previous shortcomings and identify additional components required to further define a strong software services-oriented delivery methodology.Electrical and Computer Engineerin

Beyond Surveys: Analyzing Software Development Artifacts to Assess Teaching Efforts

This Innovative Practice Full Paper presents an approach of using software development artifacts to gauge student behavior and the effectiveness of changes to curriculum design. There is an ongoing need to adapt university courses to changing requirements and shifts in industry. As an educator it is therefore vital to have access to methods, with which to ascertain the effects of curriculum design changes. In this paper, we present our approach of analyzing software repositories in order to gauge student behavior during project work. We evaluate this approach in a case study of a university undergraduate software development course teaching agile development methodologies. Surveys revealed positive attitudes towards the course and the change of employed development methodology from Scrum to Kanban. However, surveys were not usable to ascertain the degree to which students had adapted their workflows and whether they had done so in accordance with course goals. Therefore, we analyzed students' software repository data, which represents information that can be collected by educators to reveal insights into learning successes and detailed student behavior. We analyze the software repositories created during the last five courses, and evaluate differences in workflows between Kanban and Scrum usage

Управління міжнародним бізнесом: Agility Journey для високотехнологічних компаній

The purpose of the article is the development of recommendations for the business maturity determination and measurement in the implementation of the agile approach for high-tech companies. Methods of analysis of documents, observation, personal and in-depth interviews, case studies have been used in the research. The findings of the research: Business Agility Journey has been suggested for defining the state of the maturity of the company and conducting express diagnostics of agility. Agile Project Management Journey has been developed for the identification of weaknesses by the companies in the path to agility, as well as for the determination of events for the transition from the traditional to the agile approach. Personal Agility Checklist has been designed for testing the soft skills of employees for the presence of the agile mindset. Research limitations include the study of the maturity of companies in the IT industry. Practical implications are based on the use of suggested Agility Journeys in defining the state of maturity and main problems on the transition path. Also, Personal Agility Checklist will help to check the agility of the future employees. The originality of the article is based on the uniqueness of the Agility Journey that has been developed for the first time. Further research on this topic should be focused on the development of an agile mindset as a prerequisite for the provision of agility in the company.Метою статті є розробка рекомендацій щодо визначення та вимірювання зрілості бізнесу при впровадженні еджайл-підходу для високотехнологічних компаній. У дослідженні використовуються методи аналізу документів, спостереження, особистого та глибинного інтерв’ю та кейс-стаді. Розроблено Business Agility Journey для визначення стану зрілості компанії та проведення експрес-діагностики еджайльності. Agile Project Management Journey було розроблено для визначення компаніями своїх слабких сторін, а також заходів для переходу від традиційного до еджайльного підходу. Personal Agility Checklist був створений для перевірки «гнучких навичок» (soft skills) співробітників на наявність гнучкого мислення (agile mindset). Обмеження досліджень включають вивчення зрілості компаній ІТ-галузі. Практична значущість ґрунтується на використанні запропонованих Agility Journeys для визначення стану зрілості та основних проблем на шляху переходу. Також Personal Agility Checklist допоможе перевірити еджайльність майбутніх працівників. Оригінальність статті базується на унікальності Agility Journey, яка була розроблена вперше. Подальші дослідження на цю тему доцільно зосередити на розвитку гнучкого мислення як передумови забезпечення еджайльності в компанії

BPM, Agile, and Virtualization Combine to Create Effective Solutions

The rate of change in business and government is accelerating. A number of techniques for addressing that change have emerged independently to provide for automated solutions in this environment. This paper will examine three of the most popular of these technologies-business process management, the agile software development movement, and infrastructure virtualization-to expose the commonalities in these approaches and how, when used together, their combined effect results in rapidly deployed, more successful solutions

Migrating agile methods to standardized development practice

Situated process and quality frame-works offer a way to resolve the tensions that arise when introducing agile methods into standardized software development engineering. For these to be successful, however, organizations must grasp the opportunity to reintegrate software development management, theory, and practice

EFFICIENT TEAM BUILDING FOR ON-TIME PROJECTS

When we think to software development projects we consider that a strong set of requirements is defined and team members always follow initial planning. Well, this was a specific orientation in traditional software developments methods and methodologies. In a current competitive business environment this attitude leads to fail in software development projects. This paper aims to highlight the importance of agile approach focused on meetings and team building and to give examples based on our experience in software development in industrial field for financial and energy sectors. This paper is the result of collaboration between university (business informatics, psychology, and finance) and business environment (internal software development projects).agile software development, team/group building, CMMI, project management