Our two-day SAFe for Teams course goes well beyond Scrum. It teaches Lean thinking tools, roles, processes, and the software engineering practices necessary to achieve the code quality you need to scale Scrum to your enterprise business context. The course is intended for new teams in an enterprise agile adoption program or can be used to re-baseline existing Scrum teams as required for scaling.
The course consists of lecture, experiential activities, and exercises to begin building actual team backlogs in preparation for the agile transformation. By the end of the course, teams will be ready for their first program-level release planning meeting, part of the Scaled Agile Framework (SAFe) Agile Release Train (ART).
The course begins with the principles of scaling: Lean thinking tools, Agile development practices at scale, and an overview of the Scaled Agile Framework.
Following this, teams learn the best practices for building quality software in a timebox. Course Outline:
Team Structure:High performing agile teams, the Scrum Master role, and the Product Owner role. At scale, teams, Scrum Masters, and Product Owners have additional responsibilities and challenges.
Building Backlogs Writing user stories and other backlog items, sizing and prioritizing using lean economics via Weighted Shortest Job First, writing acceptance criteria, and building acceptance tests. At scale, team backlogs are part of the enterprise backlog model for integrating with the program and portfolio.
Sprint Execution Planning, backlog grooming, tracking, demoing, and continuous improvement. At scale, these include team-level and program-level ceremonies and events.
Software Engineer Practices Strategies to avoid "waterfalling" a sprint, TDD, ATTD, automated testing, and continuous integration. At scale, technology and practices must also facilitate distributed development.
Launching the Agile Release Train (ART) Preparation for the first program-level Release Planning Meeting.
Agile and DevOps practices and culture are key to the success of Fujitsu Americas. The Agile/DevOps Center of Excellence has identified a number of key learning resources that should help you move through proficiency levels
While the focus for many Fujitsu projects involves the delivery of IT solutions, managing and delivering the related business transformation is a core service and skill set within Fujitsu.
Business Transformation takes many forms and names, such as organizational development, organizational design, change management, process redesign. It ensures that a cohesive solution is created that enables clients to fully realize the benefit and value from their programme investments. The intent for the PM Delivery Forum presentation is to provide an overview of a recently completed business transformation project to demonstrate why understanding and managing the business side of an IT project is critical to success for both project managers and clients." Play recording
DevOps is a popular set of principles and techniques that are being promoted within Fujitsu, to be adapted to the context of client and engagement.
The course provides an introduction to current DevOps principles, practices, vocabulary and supporting automation.
This course is mapped to a corresponding certification offered by the DevOps Institute. We use course materials provided by DOI. After attending this course, the participant will be eligible to take the DevOps Foundation certification exam.
This learning event provides an introduction to the Agile Delivery adaptation. It includes an overview of its phases, activities, deliverables, techniques and main roles.It also addresses how to manage an Agile project.
Agile development projects are always focused on the end user, and the creation of user stories plays an integral role in defining end user requirements to ensure the software meets all of their needs.
However, if you're new to agile development, you may be unsure of how to best utilize user stories in your development process.
Fortunately, this resource offers a detailed description of user stories and explains how they function within agile methodology. Read on for an explanation of the 3 Cs of user stories:
The fun way to learn about Agile/Scrum, prepare for Scrum Master certification / Agile certification (CSM, CSPO, PSM, or PMI-ACP), and debunk popular misconceptions.
There are six videos addressing
Introduction to Scrum
Backlog Refinement Meeting
Sprint Planning Meeting
Daily Scrum Meeting
Sprint Review Meeting
Sprint Retrospective Meeting
Each has quizes to stress learning.
Also links to other content to understand Agile & Scrum.
Inspirée d'un livre écrit par Mary et Tom Poppendieck, cette présentation est une adaptation de l'approche Lean fondée sur le système de production de Toyota dans le domaine des TI.
Après la récapitulation des sept principes de développement de logiciel Lean, 24 points de vue présentés en image proposeront une approche différente pour résoudre des problèmes éventuels dans le domaine des TI.
Après un rappel des 7 principes du Lean Software Development, 24 points de vue imagés proposeront à l'apprenant d'aborder différemment les problèmes qu'il pourrait rencontrer dans le domaine des TI.
Le développement logiciel AGILE regroupe un ensemble de méthodes de développement logiciel fondées sur le développement itératif et incrémentiel, en fonction duquel les exigences et les solutions évoluent grâce à la collaboration entre des équipes multifonctionnelles auto-organisatrices. Il favorise la planification adaptative, le développement et la livraison évolutifs, et une approche itérative à jalon fixe, tout en encourageant une réaction rapide et souple au changement. Il s'agit d'un cadre conceptuel qui favorise les interactions prévues tout au long du cycle de développement. Le Manifeste Agile a mis de l'avant ce terme en 2001.
La réunion de mise au point (Scrum) est l'une des méthodes fondées sur l'approche de développement logiciel Agile. C'est un cadre itératif et incrémentiel de gestion de projet souvent utilisé pour le développement logiciel AGILE du génie logiciel. Bien que l'approche Scrum ait été à l'origine proposée pour la gestion des projets de gestion de développement de produits, son utilisation s'est concentrée sur la gestion des projets de développement logiciel, et on peut s'en servir tant pour diriger des équipes de maintenance de logiciel que comme une approche générale de gestion de projet ou de programme.
Agile is an umbrella term used to describe a general approach to software development. Though there are many agile incarnations, all agile processes, including Scrum, emphasize teamwork, frequent deliveries of working software, close customer collaboration, and the ability to respond quickly to change.
This Power Point presentation contains the latest wins from the New York office that pertain to Salesforce in various industries but mostly, the financial services sector. It is available to help turn our RFP's into winning proposals.
Agile approaches to software development promise many advantages: shorter schedules, more productive teams, products that better meet customer expectations, higher quality, and more. In this talk, Mike will explain how agile teams achieve these goals by avoiding the seven deadly sins of project management. Covered will be sins such as gluttony, sloth, lust, opaqueness, and more. Giving in to one of these temptations can result in a failed or canceled project.
One of the challenges of agile is coming to grips with the role of leaders and managers of self-organizing teams. Many go to the extreme of refusing to exert any influence on their teams at all. Others retain too much of a command-and-control style. Leading a self-organizing team can be a fine line. In this session you will learn the proper ways to influence the path taken by a team to solving the problems given to it. You will learn how to become comfortable in this role. You'll understand why influencing a self-organizing team is neither sneaky nor inappropriate but is necessary.
Peter Blasina, Australia's GadgetGuy, discovers how Bruce Loxton, owner of Kimberley Kampers, has been able to grow his business from 4 to 20 million in turnover, while operating out of his wife's clothing store. With his factory nearly 900 miles away, and a sales team spread across Australia, Bruce uses his iPad, the cloud, Salesforce and some customised applications from the App Exchange to stay on top of operations - and ahead of his competitors.
Recording of a live demo with Salesforce Foundation partner roundCorner. roundCorner demonstrates how their product roundCampus is being utilized at top-tier universities for corporate relations, advancement, recruiting and career services. Presented by Dan Lammot, Founding Partner of roundCorner.
We leverage the combination of cloud computing and Software as a Service (SaaS), with its emphasis on productively creating well-tested, maintainable, reusable code, to let "one-pizza" teams of Berkeley undergrads design, develop, test, and deploy their own SaaS applications. Iteration-based agile development rewards regular progress, test-first design results in students actually enjoying testing, and cloud computing showcases deployed projects to friends, colleagues, and future employers, all while students absorb "big ideas" such as higher-order programming and metaprogramming.
I'll also discuss other uses of cloud computing at Berkeley from lower-division through graduate CS courses.
This course is intended for people having an interest in testing web applications. When this course is complete, you'll be able to write tests that effectively test your applications but also to integrate Selenium in your existing testing processes following the good practices that this tool requires.
Agile Project Planning requires a team to do the tasks from a prioritized list, break the tasks into small ones and then execute each iteration within the estimated time frame.
A key distinction between Agile Project Planning and the traditional or standard project planning is that Agile Project Planning is expected to be collaborative in nature and wider in scope as the entire team partakes in planning and scheduling.
Jason Fried has a radical theory of working: that the office isn't a good place to do it. He lays out the main problems (call them the M&Ms) and offers three suggestions to make work work:
- Switch from active communication to passive communication
- Cancel your meetings
Module e-Learning Macroscope destiné à toute personne désirant améliorer sa compréhension de l'approche agile de Macroscope. Des questions et exercices vous permettent de tester vos connaissances sur le sujet. Vous y trouverez aussi des notes, trucs et questions fréquentes.