THE SCRUM GUIDANCE FOR IT SERVICE SUPPORT DOMAIN AND SQA TO GENERATE SUCCESSFUL AND QUALITY SOFTWARE

The article is presenting how to implement the framework of scrum in IT service support domain and software quality assurance (SQA). Basicly, scrum framework is being used in other software development methods such as agile, but the reseach found that there is merely a few could support the software development. This framework could be implemented in small, medium and large projects. By promoting the usage of scrum framework could add more valu to organization and reach its goal. The collection of scrum framework implementation from previous researcher could present the real example of scrum framework in IT service domain and SQA. As this framework is still new in practice to IT domain, so that the guidance of this scrum framework will help developer to have more experience in applying in any software development projects. As the result, the company will enhance their business valu

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

Scrum2Kanban: Integrating Kanban and Scrum in a University Software Engineering Capstone Course

Using university capstone courses to teach agile software development methodologies has become commonplace, as agile methods have gained support in professional software development. This usually means students are introduced to and work with the currently most popular agile methodology: Scrum. However, as the agile methods employed in the industry change and are adapted to different contexts, university courses must follow suit. A prime example of this is the Kanban method, which has recently gathered attention in the industry. In this paper, we describe a capstone course design, which adds the hands-on learning of the lean principles advocated by Kanban into a capstone project run with Scrum. This both ensures that students are aware of recent process frameworks and ideas as well as gain a more thorough overview of how agile methods can be employed in practice. We describe the details of the course and analyze the participating students' perceptions as well as our observations. We analyze the development artifacts, created by students during the course in respect to the two different development methodologies. We further present a summary of the lessons learned as well as recommendations for future similar courses. The survey conducted at the end of the course revealed an overwhelmingly positive attitude of students towards the integration of Kanban into the course

Programming patterns and development guidelines for Semantic Sensor Grids (SemSorGrid4Env)

The web of Linked Data holds great potential for the creation of semantic applications that can combine self-describing structured data from many sources including sensor networks. Such applications build upon the success of an earlier generation of 'rapidly developed' applications that utilised RESTful APIs. This deliverable details experience, best practice, and design patterns for developing high-level web-based APIs in support of semantic web applications and mashups for sensor grids. Its main contributions are a proposal for combining Linked Data with RESTful application development summarised through a set of design principles; and the application of these design principles to Semantic Sensor Grids through the development of a High-Level API for Observations. These are supported by implementations of the High-Level API for Observations in software, and example semantic mashups that utilise the API

An ontology of agile aspect oriented software development

Both agile methods and aspect oriented programming (AOP) have emerged in recent years as new paradigms in software development. Both promise to free the process of building software systems from some of the constraints of more traditional approaches. As a software engineering approach on the one hand, and a software development tool on the other, there is the potential for them to be used in conjunction. However, thus far, there has been little interplay between the two. Nevertheless, there is some evidence that there may be untapped synergies that may be exploited, if the appropriate approach is taken to integrating AOP with agile methods. This paper takes an ontological approach to supporting this integration, proposing ontology enabled development based on an analysis of existing ontologies of aspect oriented programming, a proposed ontology of agile methods, and a derived ontology of agile aspect oriented development

Adaptive enterprise architecture drivenagiledevelopment

Agile development practices focus on developing and delivering working software systems in small iterations with minimal documentation. However, locally project focused agile practices overlook the need for holistic enterprise architecture. Lack of enterprise architecture in agile, especially in the large agile environments, may lead to a number of problems such as technical debt, unnecessary re-work, inconsistent communication, locally focused isolated architecture, design and implementation. There is a missing link between the enterprise architecture and agile development. Enterprise architecture is a strategic capability that should enable and enhance agility of agile development. However, organisations are not sure how best to approach strategic enterprise architecture capability for supporting agile development. This paper proposes and demonstrate the applicability of an integrated adaptive enterprise architecture driven agile development approach for large agile environments

Agile Succes Factors : a qualitative study about what makes agile projects successful

Various studies show great improvements in software projects when agile software development is applied. However, there are still remaining problems and there are also reports about project failures in the agile community. This raises the question of what factors distinguish successful agile software projects and teams from less successful ones? The authors of the Swiss Agile Study wanted to shed some light on these questions. We conducted a qualitative interview study with eight successful agile IT companies. We asked them about the essential success factors in their agile projects. The findings are divided into three different categories: Engineering practices, management practices and the values, or culture, they live. On the engineering level it was found that these companies apply many technical practices in a very disciplined way, with a strong emphasis on quality assuring practices like unit testing, continuous integration and automation, and clean coding. On the management level it was pointed out that clear requirements, which are verified and validated in very close collaboration with the customer, are essential. The same was true for very close communication within the team. The third aspect that was found, was that in each successful team there was a kind of Agile Champion who motivated and inspired the team to use agility. On the value level we found that successful agile teams live a culture of openness and transparency. They establish an agile culture at least on the team and organizational level (we found only one company who had established the agile method in the whole company). Third, they live an attitude of craftsmanship, being proud of their work and striving for high quality work. Finally we noticed, that while putting high emphasize on the above practices, mature agile teams start adapting these practices and the agile process to their needs, when they notice that some of the practices do not work or that following the recipe is insufficient. A constant probing, sensing and appropriate responding was observed. This is the typical pattern for moving forward in complex adaptive systems. Applying a sense-making methodology like the Cynefin framework, theoretically explains the observations in the present study. Companies should therefore be aware, that software projects are often located in the complex domain, i.e. can be modeled as complex adaptive systems. These kinds of problems rather require emergent practices instead of good or best practices and an understanding of the implications of complexity theory is of merit

Requirements Engineering for Globally Distributed Teams using Scaled Agile Framework

As large organizations are striving to deliver software at a faster pace and to keep up with the latest trends, they are in a transformation stage of adopting to Scaled Agile Framework (SAFe). SAFe is a framework for implementing agile practices at enterprise level and it provides a roadmap for portfolios, programs and teams. Large organizations adopting to SAFe are facing challenges in coordinating, planning and managing requirements, as they work with globally distributed teams. The goal of this thesis was to improve the Requirements Engineering (RE) process using Scaled Agile Framework in globally distributed teams. The main research method used in this thesis was action research, an iterative approach which combines theory and practice. The empirical study was conducted in a large project that used SAFe and had eight globally distributed teams. In order to investigate the challenges faced by globally distributed teams, analysis of the existing literature and RE process flow in SAFe was important. It served as a good input to understand which good RE practices can be applied in the empirical study. The results of the study show that visually representing requirements as models and sharing domain and system knowledge through Community of Practice (CoP) reduced ambiguity in requirements. The good RE practice applied in SAFe, of working and improving collaboratively with the globally distributed teams helped in better coordination and managing of requirements. In addition to this, it was also essential to have SAFe training to develop clear and shared understanding of the framework and RE process. The lessons learned from the empirical study indicate that a well-organized PI planning is the key RE practice of SAFe in providing the big picture of requirements to all members in distributed teams. In addition, Community of Practice (CoP) can be a key RE practice of SAFe in sharing knowledge such as business domain, system knowledge, skills and techniques, and experiences