Ce mémoire fait tout d’abord l’état de l’art des filtres reconfigurables (passifs et actifs) pour les radiocommunications. Les différentes architectures de réception sont comparées pour déterminer celles qui sont les mieux adaptées aux récepteurs de type multistandard. Les concepts de radio logicielle et de radio cognitive ainsi que la façon de les mettre en œuvre sont ensuite indiqués afin de souligner l’intérêt d’utiliser des filtres reconfigurables. Les notions de filtres réglables, reconfigurables et agiles qui sont alors comparées illustrent tout l’intérêt des filtres agiles. Une nouvelle théorie qui permet pour la première fois la réalisation de filtres passe bande du second ordre entièrement actifs à fréquence agile est ensuite introduite. Un amplificateur de contre réaction dont le gain est réglable permet de modifier facilement la valeur de la fréquence centrale du filtre obtenu. Cette théorie est ensuite généralisée et ses nouvelles propriétés sont étudiées. Il en résulte alors une plage de réglage de la fréquence beaucoup plus étendue. Des filtres passe bande ont été réalisés en mode courant en technologie SiGe BiCMOS 0.25 µm de STMicroelectroincs à partir de convoyeurs de courant contrôlés (CCCII). Les résultats de simulation obtenus pour ces différents filtres confirment les avantages de cette théorie. Ils montrent ainsi que la généralisation précédente conduit à des structures entièrement actives dont la plage de réglage de la fréquence augmente et la puissance dissipée diminue. Des résultats de mesure obtenus sous pointes pour un filtre passe bande réalisé dans la technologie précédente sont donnés. Ils sont aussi en parfait accord avec cette théorie. Cette nouvelle approche permettra de réaliser des filtres agiles pour les récepteurs multistandard de radiocommunication. / In this thesis, we explore the state of the art of reconfigurable filters (passive and active) used in radio-communications. Different receiving architectures are compared to determine the most suitable for multi-standard devices. The concept of software and cognitive radio as well as the means to implement them are indicated in order to highlight the advantage of reconfigurable filters. The concepts of tunable, reconfigurable and agile filters are compared, illustrating the advantage agile ones. A new theory which allows, for the first time, the realization of second order band-pass fully active filters is then introduced. A feedback amplifier with tunable gain allows modifying easily the center frequency of the resulting filter; this theory is then generalized and its new properties are studied. This results in a large frequency tuning range. Current mode band-pass filters are implemented in SiGe BiCMOS 0.25 µm from STMicroelectroincs using current controlled conveyors (CCCII), the simulation results confirm the interest of this theory. They also show that the generalization leads to entirely active structures whose tuning range increases while its power dissipation decreases. The measurements carried out on the fabricated chip are given; they are in perfect agreement with this theory. The new approach allows realizing agile filters for multi-standard radio-communication receivers.

The lack of knowledge regarding the perception of risks in agile project management is evident in research. With this knowledge, this study sets out to address this issue and close the gap in knowledge regarding this issue by identifying the individual perception of risk by a project leader, SCRUM master, and two system developers, and comparing the individual appetite matrices to a unified appetite matrix created by a Delphi panel. A case study at an IT consulting firm, working with several projects in parallel, in Sweden is conducted. A risk register is used to collect the data, with the principle of assisting in creation of the risk appetite matrices. The result shows that the individual risk appetites differ significantly from the group’s unified risk appetite. The group showed itself far more risk aggressive than the individual appetite which was risk aversive in relation to the group’s appetite. The lack of RM practices is evident in smaller IT firms such as these, as there are no clear standardized approaches to the mapping or classification of risks; a far more informal approach is taken.

Métodos ágeis são técnicas adequadas para o desenvolvimento de software sujeito a mudanças constantes. Essas mudanças não devem afetar o cronograma, orçamento do projeto e devem assegurar o atendimento às necessidades do cliente. Diversos valores, princípios e boas práticas de desenvolvimento e de condução de projeto são aplicados em projetos ágeis com esse objetivo. Algumas dessas práticas são relacionadas a atividade de teste de software. Este trabalho teve como objetivo caracterizar a atividade de teste de software aplicada dentro de métodos de desenvolvimento ágil, buscando eliminar aspectos de teste não produtivos, identificando boas práticas e, principalmente, criando formas de acompanhar e melhorar continuamente a condução da atividade de teste. A partir da caracterização da atividade foi proposta a adoção de um conjunto de métricas para facilitar o seu acompanhamento e melhoria constante da mesma. Algumas dessas métricas de acompanhamento de testes foram implementadas na ferramenta Agile Testing Metrics Management (ATMM). O objetivo principal da ferramenta é gerenciar as iterações de desenvolvimento do projeto ágil e, também, exibir a evolução das métricas relacionadas ao código que está sendo testado e aos casos de teste desenvolvidos utilizando a ferramenta JUnit. Para validar a ferramenta e as métricas foram conduzidos estudos de casos com dois projetos de software de domínios diferentes que utilizaram métodos ágeis e testes de unidade / Agile methods are appropriate techniques for software development subject to constant changes. These changes should not affect the project schedule, budget and must ensure meeting the clients needs. Several values, principles and practices of project development and driving are applied in agile projects with this goal. Some of these practices are related to software testing activity. This study aimed at characterizing the software testing activity applied to agile development methods, trying to eliminate unproductive testing aspects, identifying good practices and especially creating ways of tracking and continuously improve the test activity. From this activity characterization, it was proposed an adoption of metrics set to facilitate the monitoring and constant improvement of the activity. Some of these testing tracking metrics were implemented in the Agile Testing Metrics Management Tool (ATMM). The main goal of this tool is to manage the iterations of agile project development and, also show the metrics evolutions regarding the code that have been tested and the test cases developed using JUnit. The tool and metrics were validated by case studies that were conducted with two software projects of different domains which used agile methods and unit testing

COSMIC metodas apibrėžia principus, taisykles ir standartinio funkcinio dydžio matavimo procesą. Šio metodo realizacija Agile projektuose, padės prognozuoti konkrečios užduoties atlikimo laiką ankstyvoje planavimo stadijoje. Netikslus darbo imlumo įvertinimas planavimo stadijoje gali tapti rimta problema, dėl ko gali nepavykti įgyvendinti projekto, arba jo dalies, laiku. Vartotojų scenarijai yra vertinami SP, kurie nėra verčiami į laikinę skalę, kas dar labiau apsunkina tikslų darbo imlumo įvertinimą pradinėje projekto ir užduočių planavimo stadijoje. Šiame darbe atliekama detali COSMIC metodo analizė, apžvelgiami esami įrankiai, skirti Agile projektams. Įsitikinama, kad nėra sukurto įrankio, leidžiančio prognozuoti vartotojų scenarijų atlikimo laiką, sujungus COSMIC su istoriniais darbų atlikimo duomenimis. Darbe iškeltų tikslų pasiekimui buvo atliktas trijų dalių eksperimentinis tyrimas kurio metu paaiškėjo, kad COSMIC metodo apjungimas su istoriniais darbų atlikimo duomenimis gali pateikti panašią ar net geresnę prognozę, lyginant su programuotojų komandos įvertinimu. Taip pat pateikiamos idėjos įrankio korekcijai, jos realizuojamos ir kartojamas eksperimentas. Aptariami gauti rezultatai ir pateikiamos išvados. / COSMIC method defines principles, rules and the process of standard functional size measurement. Method implementation in Agile projects will help forecasting the completion time for a specific task in the early planning stages. Inaccurate task capacity estimation in the planning stage can become a serious problem which in turn may lead to not being able to complete parts of the assignment or even the whole project. User stories are being evaluated as SP which are not converted into a timescale which further complicates accurate job receptivity in the early project and task planning stage. Within this paper a detailed COSMIC method analysis is being performed as well as a review of existing Agile project tools. Also making sure that there are no other tools which allow the forecast of user story completion time by merging COSMIC with task completion time history log. To complete the goals of this paper a three part experimental survey took place which determined that the consolidation of the COSMIC method with the task completion time history may result in a similar or even more accurate forecast as compared to the forecast of a team of software developers. Also new ideas for tool adjustments are included, their implementation and repeating of the experiment, review of the obtained results and findings.

Within Scrum framework the role of the product owner is critical for the success of a Scrum project. Today, there exist little empirical evidence of how the role of product owner is practiced and the challenges they are faced with. This research seeks through a multiple-case study approach to explore the role of product owners. The aim of the research was to investigate the existence of a gap between theory and practice in terms of the product owner role. Qualitative data collection consisted of eight semi-structured interviews with product owners and agile coaches which then was analyzed according to what theory of the role suggests. Results showed partly multiple factors confirming a gap, for example regarding vision, prioritizing and communication, and challenges that arise from the gap, for example concerning decision-making.

A challenge in Lean Construction is how to make it applicable when there is a high degree of complexity and uncertainty. In many construction projects there are changing project requirements, unique products and a need for actions that are highly focused on meeting customer/client expectations. Such scenarios require management methods that are characterised by being flexible and able to react to change. The aim of this thesis is to introduce a method that has such characteristics. Project Management, Lean and Agile paradigms are merged through the application of the fission and fusion approach of nuclear physics. This research is facilitated through a sequential explorative method. In the first instance, interviews with 22 practitioners in the fields of construction project management, Lean and Agile have been conducted. Then a quantitative self-administered questionnaire with 213 useful responses has been utilised to validate the transferability of the interview findings. It is concluded that Lean is not ideally suited to dealing with the dynamic nature of construction projects. Agile methods, which were developed to cope with the high levels of uncertainty inherent to IT projects, are more flexible and able to react to change. Hence utilising Agile-based methods might be the key to the successful utilization of Lean in construction. Therefore a management method based on combining Lean and Agile approaches has potential. Such an approach needs creative thinking to develop a solution that is different to that of “Leagile”. Leagile uses Lean and Agile methods in the execution phase sequentially, through using a decoupling point model to separate the two. This thesis introduces a new paradigm in which such a decoupling or separation does not take place. Rather, project management, Lean and Agile have been merged together to develop a new holistic and strategic framework. The paradigm presented in this thesis is termed “AgiLean Project Management”.

In today’s fast-paced world, there is a constant demand for better and more efficient ways of doing business. Motorola in Linköping are using the agile development framework, Scrum in their software development. A certain level of quality must also be assured of the delivered goods and services. Is it possible to use Scrum and still meet the quality requirements? This Master Thesis is performed to investigate if it is possible to achieve a quality certificate from TL 9000, the telecom industry extension of ISO 9000, when using the agile development framework Scrum. The investigation consists of interviews and observations at Motorola, Linköping, along with literature studies about quality systems and agile development. The conclusion is that it is possible to meet the TL 9000 requirements when using Scrum, under the condition that some additional processes are performed and that other parts of the organization also fulfills the remaining requirements. This is needed since there are requirements that are out of scope for the Scrum framework. Examples of the suggested additions are to follow the Scrum framework more strictly and to adopt a more specific definition of done.

This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions. A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software. In this paper, both the traditional plan-driven methods and agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented. The company's current work processes are analyzed and presented, and all collected data will be reviewed. The results of the paper shows that no initial adaptation of agile methods, Scrum in this specific case, needs to be implemented and that there is no evidence to suggest that small organizations with small development teams can not work after a formal agile methodology. Finally, a general discussion of the study will be conducted and conclusions whether the study objective has been achieved or not will be discussed. / Denna uppsats ämnar undersöka huruvida en mindre organisation med små utvecklingsteam kan finna ett värde i att lämna en fungerande utvecklingsprocess för att följa en formell systemutvecklingsmetod, ifall dessa organisationer kan hitta ett metodstöd i agila systemutvecklingsmetoder och om metoderna i så fall behöver anpassas utefter organisationens unika förutsättningar. En traditionell plandriven systemutvecklingsmetod innehåller ett antal faser som genomförs sekventiellt och en slutförd fas kan i stort sett inte återupptas. Alla krav specificeras i början av ett projekt och endast en leverans av mjukvara sker. Detta kan medföra svårigheter med att hantera till exempel förändrade krav. Agila systemutvecklingsmetoder har för avsikt att hantera förändrade krav samt möjliggöra kontinuerliga leveranser av värdefull och fungerande programvara. Under uppsatsen kommer såväl traditionella plandrivna metoder som agila metoder att förklaras närmare. Metodval för forskningen och befintliga systemutvecklingsteorier kommer att diskuteras och ett företag där studien har bedrivits kommer att presenteras. Företagets nuvarande arbetsprocess analyseras och presenteras och alla datainsamlingar kommer att gås igenom. Resultatet av uppsatsen visar på att inga initiala anpassningar av agila metoder, Scrum i det här specifika fallet, behöver genomföras och att det inte finns något som tyder på att små organisationer med små utvecklingsteam inte kan arbeta efter en formell agil metod. Slutligen kommer en allmän diskussion om studien att föras och slutsatser gällande om syftet med studien har uppnåtts kommer att diskuteras.

The Thesis purpose is in the context of system development validate the Scrum Methodology. Projects concerning information technology are difficult to manage and tend to fail in quality, time or costs. Scrum presents a new view of the system development. Better cooperation between customers and developers, continuous follow-up on daily basis and extensive communication in the development team are all characteristics of Scrum. Scrum is described as a new paradigm by its founders but has been criticized by experts of system development too. This Thesis discuss if Scrum is a better way to develop software than older models like the Rational Unified Process and the Spiral Model with focus in five factors. The result of the study is that Scrum has given system development new ways to manage requirements and methods to push the project forward. Lack of management commitment and user involvement can be better with Scrum if the model is used in the right way. Answers concerning coding and testing differ between the respondents in the study which makes it different to make conclusions regarding this factor. / Syftet med uppsatsen är att i en systemutvecklingskontext beskriva de problem som gör att IT-projekt misslyckas och utvärdera om användningen av den agila utvecklingsmodellen Scrum reducerar problemen. IT-projekt tenderar att misslyckas och de bakomliggande orsakerna är flera. Uppsatsen grupperar misslyckande av IT-projekt i fem faktorer. Ledningsstöd, användarmedverkan, projektstyrning, kravhantering samt kodning och test. Scrum är en agil systemutvecklingsmodell som av sina skapare beskrivits som ett paradigmskifte inom systemutvecklingen. Korta tidsintervaller, självgående systemutvecklare, daglig uppföljning är några av Scrums kännetecken. För att besvara syftet har en kvalitativ datainsamlingsmetod använts. En intervjuserie med tio intervjuer och en observation ligger till grund för undersökningens resultat. All insamlad data är insamlad på fallföretaget Banverket Verksamhetsstöd IT. Undersökningen har visat att Scrum ger en del nya angreppssätt främst avseende projektstyrning och kravhantering. Scrum innehåller möjligheter för ökad användarmedverkan och ledningsstöd men det krävs konkreta åtgärder från projektorganisationen om det ska lyckas fullt ut. Uppfattningar kring kodning och test skiljer sig åt beroende på vilken respondent som frågas. Det tyder på att det saknas tydliga rutiner i det här avseendet. Slutsatsen blir därmed att Scrum reducerar några av de problem som finns i IT-projekt och därmed med fördel kan användas som en best practice.

This diploma thesis aims at the development of agile software projects of an existing company. The main goal of this dissertation has been to identify and analyze the most frequent current problems of the company, then to summarize their impact and to propose the best possible way of dealing with them. As an integral part, the aim of the dissertation has also been the creation of an internal knowledge base which can help to prevent those problems from happening in future projects and to share mutual experiences. To fulfil this goal, it has been necessary to learn all the problems of the agile software development, to know the most widely used agile methodologies and some latest facts and recent trends in the area of agile projects. It has also been necessary to carry out the SWOT analysis of the company and analyze the results of the internal agile development survey. The next thing which had to be done was the identification and description of the most frequent problems of agile development projects and the assessment of the categories of projects which occur in the company and linking the problems with each of the categories. The content of the internal knowledge base was created to correspond with the results of my diploma thesis. The contribution of this dissertation is the identification and assessment of the most fre-quent problems of agile projects of an existing company, identification of possible impacts and recommendation of possible solutions. The other contribution is the identification of the project categories which are linked to the identified problems. Last but not least, the main benefit of this thesis is the creation of a new internal project management knowledge base which will help to share the experience among all the projects and in this way it will help to prevent the spread of these problems. This diploma thesis is divided into two main parts, theoretical and practical. In the theoretical part, there is a definition of "agile methodologies", a description of their typical examples and statistics as well as modern trends in the area of the development of agile projects. The practical part is divided into four chapters. They contain the results of the company's SWOT analysis and the results of the internal agile development survey. Then there is a presentation of the identified agile development problems, their possible impact and the recommendation how to deal with them. There is a full description of all the identified categories of projects and their identified problems with their assessment criteria as well as time-proven ways how to effectively deal with them. The last chapter contains and internal project management knowledge base which has been done by myself. The knowledge base may be very useful in the project management now and in the future.