background preloader

Scaled Agile Framework

Scaled Agile Framework

unSAFe at any speed | Ken Schwaber's Blog: Telling It Like It Is The boys from RUP (Rational Unified Process) are back. Building on the profound failure of RUP, they are now pushing the Scaled Agile Framework (e) as a simple, one-size fits all approach to the agile organization. They have made their approach even more complicated by partnering with Rally, a tools vendor. Consultants are available to customize it for you, also just like RUP. They are touting their processes and tools this week at Agile 2013 in Nashville. They would be at the RUP conference, but there are none. When the signers of the Agile Manifesto got together in 2001, we wanted to share our ideas about software development, a discussion that resulted in the Agile Manifeto. Individual and Interactions over Processes and Tools We wanted to undo the damage that waterfall had done to our profession, and we also hoped to ensure that RUP wasn’t seen as a viable successor. In many instances, software development has improved based on the values and principles in the Agile Manifesto. Best,

Agile Requirements Information Model (5) – For Agile Programs (b): Nonfunctional Requirements | Scaling Software Agility Agile Requirements Information Model (5) – For Agile Programs (b): Nonfunctional Requirements Posted on January 8, 2009 by Dean Leffingwell in Agile Requirements Note: This is the fifth in a series of posts describing, in more rigorous terms, A Lean, Scalable Requirements Information Model for the Agile Enterprise (AE RIM) that underlies the Big Picture Series. In this series, I’ve been collaborating with Juha-Markus Aalto, Director of Operational Development for Nokia S60 Software Unit, where a variant of the model is being developed and applied on a very large scale development project. In the last post, the Agile Requirements Information Model For Agile Programs we described those elements of the model, Features and Feature Backlog that are relevant to the Program Level of the Big Picture. Agile Enterprise Big Picture with Program Level Highlighted In this post, we complete that discussion with a discussion of Non-functional Requirements. Non-functional Requirements in Agile Development

OpenUP: Um processo ágil Alguns anos atrás, vários colegas da IBM começaram a pensar sobre como seria possível criar uma versão ágil do IBM Rational Unified Process, ou simplesmente RUP. Ao mesmo tempo em que esse novo processo deveria ser ágil , também teria que refletir as boas práticas já contidas no RUP e consolidadas no mercado de software. A partir desse momento, o time IBM formado por gerentes de metodologias , especialistas e analistas de processo começou a trabalhar em uma nova versão com a proposta de criar um novo processo enxuto, completo e ao mesmo tempo extensível. A longo do tempo esse mesmo time percebeu que seria necessária a contribuição através de conhecimentos e experiências de um conjunto muito mais amplo de pessoas. Daí então que a IBM através do projeto EPF (Eclipse Process Framework), liderado por Per Kroll (Gerente de Métodos IBM) forneceu para a comunidade Eclipse o conteúdo da versão inicial desse novo processo, até então considerada uma versão “light” e “ágil” do RUP. OpenUP 1.5.0.1

DevOps « Scaled Agile Framework In order for you to keep up with customer demand, you need to create a deployment pipeline. You need to get everything in version control. You need to automate the entire environment creation process. You need a deployment pipeline where you can create test and production environments, and then deploy code into them, entirely on demand.– Erik To Grasshopper. The Phoenix Project DevOps is a pattern, not a team. Real, tangible software development value occurs only when the end-users are successfully operating the software in their environment. Deployment Operations is an Integral Part of the Software Value Stream The goal of software engineering is to deliver usable and reliable software products to the end users. However in most cases, development teams still deliver software to deployment in large batches. Deployment Operations Must be “On the Train” In SAFe, Value Streams cover all steps of software value creation and delivery. Figure 1. 3a: Deploy to Staging Every Sprint Summary

The Agile Unified Process (AUP) Home Page Current Status I stopped work on the AUP in 2006. Since 2009 I have actively worked on the Disciplined Agile Delivery (DAD) framework. Overview is a simplified version of the Rational Unified Process (RUP). Figure 1 depicts the lifecycle of the AUP. Figure 1. Serial in the Large The serial nature of Agile UP is captured in its four phases : Inception. Iterative in the Small Disciplines are performed in an iterative manner, defining the activities which development team members perform to build, validate, and deliver working software which meets the needs of their stakeholders. Model. Delivering Incremental Releases Over Time Instead of the "big bang" approach where you deliver software all at once you instead release it into production in portions (e.g. version 1, then version 2, and so on). Figure 2. Philosophies of the AUP The Agile UP is based on the following principles: Your staff knows what they're doing. Some History Should You Adopt the AUP? The AUP isn't for everyone. The Instructions:

Agile Testing | Tester Troubles Process of Scrum · MS community blog Scrum is an extremely lightweight framework for (new) product development, or, to quote Jeff Sutherland, a “pattern language for hyperproductive software development”. After having presented the Definition (s) of Scrum it’s time to have a look at how all elements tie together in the Process of Scrum: In a first step the Vision is being translated into a Product Backlog, i.e. a prioritized list of features and tasks to create the envisioned product. Most Scrum practitioners tend to use User Stories, i.e. features for real end-users (sort of an essential Use Case). But the real core of the Scrum process is the Sprint, typically taking 2-4 weeks: So the result of a Sprint is a piece of working software, which is a perfect implementation of the principles of the Agile Manifesto: “Deliver working software frequently”; “Working software is the primary measure of progress”. More details can be found in the official Scrum Guide (by Ken Schwaber and Jeff Sutherland) at Scrum.org. Agile · Scrum

uml - How to use BPMN and use case and other diagrams together Fabasoft Folio Cloud Help 7.6.4 Releasing a BPMN Process Diagram To be able to execute BPMN processes, the processes have to be released using the context menu command “Release Process for Execution”. The process can be released for the user himself (testing purposes) or for groups that are assigned to the user. The user needs change rights on the groups. To release a process, perform the following steps: Right-click the process diagram and then click “Release Process for Execution”.If syntax errors are found, that will prevent the execution, you can view and resolve the errors.If no syntax errors are found, check the groups for which the process diagram should be released and then click “Next”. Released processes can be easily identified by the symbol. The release state can be removed by executing the context menu command again and removing the check marks for the corresponding groups. A renewed release affects only newly started processes.

Modelo de Desenvolvimento Ágil SCRUM - Devin Na faculdade, tive um trabalho de pesquisa e apresentação de metodologias de desenvolvimento de software. Meu grupo ficou com o assunto SCRUM, então acabei criando este material que pode muito bem servir para outras pessoas. O grupo do trabalho foi: Hugo Cisneiros, Moyses Santana Jacob, Stelvio Mazza e Tiago Pereira. A matéria foi de Engenharia de Software, com o professor Marcelo Pintaud. Este artigo resume e explica bem o modelo de desenvolvimento ágil SCRUM, que hoje em dia é bastante usado (inclusive usamos na empresa em que trabalho). Espero que seja de grande proveito! Introdução: Modelos de desenvolvimento de software No decorrer de vários anos o desenvolvimento de software cresceu de forma muito acelerada, principalmente pelo fato de que as ferramentas da informática se tornaram presentes em grande parte das áreas de trabalho das pessoas. Esta crescente demanda fez surgir uma variedade de estratégias de desenvolvimento de software. O SCRUM é um modelo de Desenvolvimento Ágil. 1.

Entendendo o Scrum no CEVIU | Parte 2 | CEVIU Blog Continuando o post anterior Entendendo o Scrum no CEVIU – Parte 1, falarei um pouco mais sobre como aplicamos o Scrum aqui no CEVIU. Sprint Backlog Logo após o fim da reunião de definição do Sprint, já começo a preparar o Sprint Backlog, uma planilha que exibe tudo que será realizado pela equipe durante as próximas duas semanas. Enquanto isso, o PO já analisa com mais atenção os itens do Sprint Backlog e os prioriza separadamente. Assim que o PO me envia o Sprint Backlog priorizado, já insiro as estórias em ordem de prioridade em nossa planilha, e as divido em tarefas menores, que serão pontuadas com maior precisão por todos os membros da equipe. Com as tarefas já definidas, começamos a pontuar nossas tarefas (Planning Poker). Faça o download das Cartas de Planning Poker usadas no CEVIU Planning Poker O Planning Poker é, de acordo com o Scrum, uma maneira de estimarmos nossas tarefas. A nossa estimativa é baseada no que a pessoa responsável pela tarefa fala. Bem, espero que tenham gostado!

Scandinavia's leading consultancies in Lean ang agile Software Development

Related: