Agile Management Guide
|
|
- Hugh Douglas
- 5 years ago
- Views:
Transcription
1 1 Agile Management Guide These days there is a strong push for Agile Management, as opposed to Waterfall. Personally at Castellan Systems we believe that the agility should be applied to the project development lifecycle rather than the project management. A strong project management process is equally, if not more, appropriate to an "Agile" environment. The more agile or dynamic a project environment is, the more important strong project management principles and processes are. In a fast moving project environment things can go wrong very quickly and if the project management disciplines are not strongly applied these problems may not be picked up until it's too late. Agile is sweeping the world. Well, it is if you re involved in product development. It s not new, Agile has been around for over 20 years, but it s seems to have gained traction with each passing year and is trending, as they say in social media circles. But is Agile really the miracle cure for all project woes as it s often prescribed? Of course not, but it s a fine way to manage a project, and Agile offers some unique advantages for the project leader and their team. Agile is a software development approach that has gained momentum over the years, with good reason. It addresses uncertainty with respect to product requirements and development as opposed to Waterfall, which looks to organize the project lifecycle phases in sequential order Initiation, Planning, Execution and Closure. What Is Agile? More and more teams are going Agile these days. Everyone working in software dev is either using Agile or they are learning how to use Agile. And now Agile has spread to be adapted by other kinds of teams, too, like marketing and sales. But what is Agile? Is it a methodology, as some insist, or is it not, as other protest? Well, it does seem to follow certain principles, and however loose and collaborative it may be, remains fixed to those principles. Agile Agile is best known for its manifesto (primarily for software development) where solutions evolve through an iterative, collaborative process. Generally speaking, it is founded on the principles of adaptive planning, evolutionary development and early (and often) delivery with the end user in mind. But Agile isn t a magic bullet that can pierce any project to reap the same positive results. Agile offers a kind of structured methodology, or approach, or whatever definition you prefer. Agile has an almost cult-like following, and many advocates don t believe it s a methodology at all.
2 2 Some say that Agile is a philosophy of software development, and Scrum is a framework to apply this philosophy. Good software development practices are the practical methodologies that make it all work. Agile is a set of values and principles. But whatever you do, don t confuse Agile with Project Management. Agile is about building a product and not about managing a project; there is more to Project Management than simply getting the product built. That may be true, but it s also a system of methods used in a particular area of study or activity, which is the textbook definition of Agile. Controversy aside, Agile is well suited to those continual deployment-type projects where the target is moving, an environment where priorities are constantly changing and you have highfunctioning collaborative teams. However, if your project has hard deadlines and pre-determined product spec, one that is immovable for whatever reason, then Agile may not the way to go. You might need a different methodology, like Lean or KanBan or Waterfall-style structured projects, or you might benefit with a hybrid approach. Even this, though, is debatable, as the proponents of Agile note it can used for fixed project work, as well. Despite the lack of agreement on what Agile is and what it s good for, and even the possible divisiveness of such an argument, Agile remains popular and deserves serious consideration for anyone leading a project. So, at the start of any project, you should figure out if Agile is the best, or only, approach, for you. To determine the proper course of action, ask yourself these three questions. 1. Is my project completely structured? There are projects where the deliverables are set in stone and a project leader can work back from that to develop a linear path to reach that goal. This is not an ideal Agile environment, even if there are those who would disagree. Think of the classic Waterfall projects such as infrastructure improvements or construction projects or building the Hoover Dam. In these types of projects, there are defined plans and sequential timelines requiring a fixed structure, and while Agile advocates say Agile can apply, it may not be ideal. For example, first environmental studies need to be conducted, and approved, and then architectural renderings that define engineering specs all need to be finalized before pouring the concrete. All those deliverables are set in stone, so to speak. 2. Does my project require some structure? There are projects that neither fall under the highly structured or clearly Agile category. They may require a hybrid approach. Portions of the project could benefit from Agile, such as dev required for a new website build related to a new retail store launch. Whereas other parts of the project, might be more structured and be more suited to a traditional planning methodology, such as the construction of the new store interior and the manufacturing of the clothing line. It s possible to use both on a single, larger project, but likely each would be considered sub-projects, and managed distinctly. 3. How hands-on are my stakeholders? There are times when stakeholders are going to want change and want to see that change implemented quickly. They will give their teams marching orders, but are content to step back and allow the team to arrive at solutions in their own fashion. These stakeholders are perfect for Agile projects. Then there are stakeholders who demand a greater control over the course of a project s overall progress. They may be delivering the fixed product requirements and prioritized backlog to the team to implement in a more topdown fashion. This could be either due to leadership style, or that the product or project requires more defined deliverables at the outset. In short, when the roadmap that is immutable and timelines for deliverables are fixed at the start of a project, then Agile may not be the best choice.
3 3 There s differing opinions on that, too, however, and some believe Agile can be applied to projects with immutable and fixed timelines. It s one of the things that s so great and frustrating about Agile: it s a flexible approach with sometimes passionate believers that see its benefits in every potential project application. That can be helpful in that it keeps one open to the many possible applications of Agile, but it s important that your stakeholders are well informed about the Agile process, so they can understand its benefits, too. Agile is a great tool for projects, especial if you re working incrementally, seeking user feedback and charting bugs, so you can adjust the product while in production, Agile can be your guiding principle. But despite of the seemingly fluid definition of Agile, like any tool you have to use the right one for the right job. You want to make sure the research is done to know your stakeholders and know all aspects of the project (or sub-projects) to determine what will be best for you going forward. If it s Agile, then by all means get on board, but being flexible to support to other approaches and hybrid approaches, will better ensure the success of your project. What Are the Right Conditions for Agile? Agile is best used when product requirements are uncertain. Time is used more efficiently to engage the product owner and the Scrum team, starting with the use of user stories. User stories are a brief description of features and functionalities the product owner wants to have developed. The product owner and the Scrum team then takes these software features and creates a to-do list called a product backlog. Once the product backlog is established the Scrum team creates a sprint backlog. These features are then scheduled for release in sprints. Sprints are scheduled releases of features designed to develop and deploy small portions of the product at a time. The product owner and Scrum team will meet daily (daily Scrum) to review the development progress. This approach helps to address the issue of product or requirement uncertainty. Develop some, test, gather feedback and continue developing until the product owner is satisfied with the end results. When is Agile Not the Best Approach? Agile is not always best, such as when there is little uncertainty regarding requirements. Product development efforts where there is a solid history to use as a baseline for a new project may be better suited for a waterfall methodology. Managing the build of a data center is a good example. The planning effort depends on solid requirements and a specific sequence of activities to be completed in order. You cannot build a little and test a little with a data center. It s impractical.
4 4 So, When Is Agile the Way to Go? Now that we have a good idea what Agile is, what kind of environment it s most suited for and those project that are better served with a more traditional methodology, it s time to look at where Agile makes the most sense. There are many, and here are a few: When requirements are uncertain The Agile iterative planning approach allows development to begin sooner and makes the product owner part of the development process. There is no need to spend six months documenting requirements that may or may not result in what the customer wants. In developing a new product feature the product owner can visualize the feature sooner allowing his or her feedback to become a part of the development process to deliver the product sooner. Software development projects are best suited for Agile Software development projects allow for parts of the overall systems to be developed, tested and delivered. This means specific features can be rolled out sooner. Sprints allow these features to be scheduled for testing and deployment separately from each other allowing the development scheduled to be as efficient as possible. Teams that are co-located benefit from an Agile approach (daily scrums) A key to the Agile approach is the daily scrum meetings. The daily scrums allow the team to discuss status, roadblocks and input from the product owner. Having these meeting in person to update the scrum board is optimal. Team members who are co-located can approach and update the scrum board at any time. This helps with team collaboration. Proactive Product Owners Real-time feedback is key for success in Agile. This replaces the need for cumbersome documentation that may never really convey the true requirements of the product owner. A product owner that is engaged and provides the development team with constant feedback allows the team to develop the right product sooner. Product owners should attend the daily huddles and vocalize their wants, likes and dislikes. This will allow the development team to produce a product the product owner wants. Teamwork and collaboration teammates who show initiative Social accountability is a key driver in the Agile approach. Agile looks to create an environment where teams manage themselves to an extent. Scrum Masters look to create a team that is proactive and shows initiative. If a team member is not stepping up to produce or become engaged the Scrum masters expects their teammates to look to help, encourage and motivate each other. The Scrum Master leads by example to set the tone for the team to encourage and hold each other accountable. Willingness to fail and learn Fail fast and learn even faster. Prototyping and feedback are essential tools in Agile. Traditional development attempts to map out all requirements before development begins, which may not be a good use of time, especially when developing what will be a new product. Develop something now! Even if it is not what the product owner wants in order to get feedback as you continue to develop. Management support of the Agile framework and its culture of empowering teams Agile can present a shift in culture and expectations for an organization, as it encourages teams to become empowered to make decisions and take risks. In contrast, a traditional development organization a Project Manager may provide clear direction, while an Agile Scrum master focuses on allowing teams to provide direction and recommend what is best for the development of the product and the product owner. Management must provide the latitude necessary to allow the team to thrive by providing guidance and direction and not try to dictate every move. The embrace of Agile is exciting. It provides one more tool in the project leader s toolbox with which to address the progress of a project. Like any tool, there are tasks that it s better at and those which it is not as well designed for. But we re all better project managers with more to choose from than less. The Case for Managing Agile Projects You want to create the most valuable software possible as determined by your stakeholders in the least amount of time and for the lowest cost. There are many different methodologies you can choose from to deliver your project, from Agile to Waterfall or a hybrid of the two. So, what do you do?
5 5 The Tension on Agile Projects You need a solid plan and a clear picture of what your project will deliver and a way to control and monitor progress while at the same time being able to release the most creative and productive energy of your project team. But is it possible to think everything through in advance, or is it better to think things through as you go, and still end up with the results your stakeholders want? There s an inherent tension here, be it a push and shove or a top-down versus bottom-up. It s like the yin and yang of project management. The answer, like Buddhism, is in taking the middle path or approaching things from somewhere in between. That doesn t mean being a project manager on a large Agile project isn t tense. You can feel that tension and you need to resolve it How to Resolve the Tension on Agile Projects Start by answering one of the biggest questions on your project, What is value? Defining value will take a lot of collaborative effort among team members and stakeholders. Together you will determine what you actually want to see in the end, based upon value. Here are some guidelines for determining value: You need something of value that connects what the developers are doing to what the stakeholders want, and a process to negotiate that throughout the development project. You want requirements that are at a high enough level to stay out of the developers way, yet provide value by giving sufficient detail to guide and empower the Scrum teams.
6 6 Top-level requirements must be understandable to allow for clear integrated testing to show if Agiledeveloped features satisfy those requirements and provide the value desired. You need a well-defined end state so that everyone knows where you re going and what value is being created. You need a well-defined yet flexible timeline to get where you re going to realize the value. You need milestones to do value assessments to determine where you are in the project and if course corrections are needed. Agile Case Study Let s say you are on a large and complex software development project. There are numerous Scrum teams, in multiple locations and under different organizations, but all on the same project. The tempo is fast, with new sprints every two weeks. There is a constant stream of meetings sprint planning, design reviews, requirements meetings, integrated test planning, Scrum of Scrums and more! The wheels are turning, but where is it all going? How do you sort through all of the activity and ask the right questions? How do you determine what s going right, what s going wrong and what is needed? Ask these three basic questions: What are we building? What is clear and what not? How will we know when we are done? By when? And how can we monitor our progress toward getting done what we know and prioritize, and clarifying what we don t yet know and make course corrections along the way? How can we do it at the needed quality level, for the least cost, and with the most efficiency? It seems, based on these questions that it s all about controlling what we can in the short to medium term and then figuring out the rest along the way. You want to empower people to contribute along the journey, assuring stakeholder concurrence and moving toward an increasingly clear picture of an end state of value. This last point moving toward a clear picture of the end state is where a lot of Agile projects can come up short, simply because they are too short-term, incrementally focused and lack an eventual longer-term goal. The Value of the Agile Approach The reason for Agile in the first place is that in software development, because of changes in technology, technical complexity and rapidly changing needs, it is hard often impossible to know exactly what you will need at some point down the road. As a result, a healthy acceptance of the fact that you cannot know it all up front can help you to adopt to a more Agile mindset. A drive for clarity on the end state can help you to properly guide the Agile work to a yet unknown place where stakeholders will be satisfied. Back to the case study on this complex and challenging agile project: How do you know when you are getting there? Can you just be satisfied to say that we are making progress? My answer is a bit trite: You cannot be satisfied that you are making progress until you are satisfied. Going a little deeper, you know that you, your team and your stakeholders are on a learning curve. At the same time you need to make progress. In large part, it s all about tempo. It s about setting up a system to ensure that all these things are happening. Agile accommodates this challenge beautifully. It enables you to be managing a relatively short duration project let s say six weeks plus or minus while at the same time chasing after that vision for the ultimate end state. Using a rolling wave, you are constantly managing this short term project that has 95% clarity, and closing out bits and pieces while you push on to the next set of bits and pieces that come into clear view.
7 7 Clarity on the final end state might be 50% at best. It s initially a bit like hitting a golf ball toward the flag. At first, you know that you can hit in the general direction of the flag although often you cannot even see the flag, but just know it s out there. So you start out with a strategy about how to get down the fairway considering wind, slopes, hazards and your own knowledge and capabilities and into a position where, as each shot is taken, you are closer to the green, where you can finally focus on getting the ball into the hole. It s the ultimate balance of short-term and long-term. Strike a Balance on Agile Projects In the final analysis, managing an Agile project is a process. You need to come to grips with what you do and don t know, and create a system for filling in the blanks as the project unfolds. You assemble the team, develop an ecosystem and manage in chunks of short duration while you figure out the rest. In the process, you deliver early and often. The one constant across all methodologies is the use of good tools designed to get the job you re working on done right. There are many tools out there, including those from Castellan Systems. To see how it can help you plan, monitor and report in real time, check out the free 30-day trial. Acknowledgements These articles were originally published by ProjectManager.com Copyright 2015 ProjectManager.com 3420 Executive Center Drive, Austin, USA 78731
Agile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationAHGILE A N D B O O K
AGILE HANDBOOK OVERVIEW 2 OVERVIEW This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people: Someone who is looking for a quick overview on what
More informationWaterfall model is the earliest SDLC approach that was used for software development.
1 Waterfall Model Guide These days there is a strong push for Agile Management, as opposed to Waterfall. Personally at Castellan Systems we believe that the agility should be applied to the project development
More informationSoftware Development Life Cycle
Software Development Life Cycle Author : harvix-distrogmail-com When people are asked to define the SDLC (Software Development Life Cycle), they often come up with something like the following: 1. Planning
More informationAgile Software Development Techniques for Small Scale Research Projects. how to not go down the rabbit hole
Agile Software Development Techniques for Small Scale Research Projects how to not go down the rabbit hole Henriette Koning Senior Manager Software Delivery But first... Henriette Koning (me) We will talk
More informationAgile Essentials Track: Business Services
Agile Essentials Track: Business Services Presenter: Mark Thomas Synopsis Are you a victim of building the wrong solutions slowly? If so, you re not alone, and considering an Agile approach may be the
More information4 Steps To Scaling Agile Across The Enterprise. The Guide To Agile At Scale
4 Steps To Scaling Agile Across The Enterprise The Guide To Agile At Scale Portfolio for Jira is a powerful Jira Software add-on for large organizations that want to scale agile practices, linking agile
More informationManaging Projects of Chaotic and Unpredictable Behavior
Managing Projects of Chaotic and Unpredictable Behavior by Richard Dick Carlson Copyright 2013, Richard Carlson; All Rights Reserved 1 Managing Projects of Chaotic and Unpredictable Behavior Dick Carlson,
More informationSEPTEMBER 2018 The Agile Team s Playbook to Doing Agile
SEPTEMBER 2018 The Agile Team s Playbook to Doing Agile A how-to guide for agile practitioners Agile is an umbrella term for a variety of work-management approaches that share common principles, among
More informationAGILE methodology- Scrum
AGILE methodology- Scrum What is Agile? This is one of the biggest buzzwords in the IT industry these days. But, what exactly is agile? The Agile model provides alternatives to traditional project management.
More informationAgile leadership for change initiatives
Agile leadership for change initiatives Author Melanie Franklin Director Agile Change Management Limited Contents Introduction 3 Agile principles 3 Introduction to Agile techniques 6 Working in sprints
More informationAGILE SOLUTIONS. Agile Basics
AGILE SOLUTIONS Agile Basics info@one80services.com one80services.com AGILE SOLUTIONS Agile Basics Table of Contents 2 Who We Are 3 What Is Agile? 4 Agile Values 5 Agile Principles 6 Agile Development
More informationThe Agile PMP Teaching an Old Dog New Tricks
The Agile PMP Teaching an Old Dog New Tricks Why are we here today? What is Project Management? When will the project be done? How much will it cost? Do we all agree on what done looks like? What are the
More informationAnnual STATE MARKETING REPORT
st Annual STATE OF AGILE MARKETING REPORT THE EVOLUTION OF THE AGILE MARKETING REVOL UTION Wanna hear something cool? You re reading the 1st Annual State of Agile Marketing Report, and that title isn t
More informationARCHITECTING PROJECT MANAGEMENT for Enterprise Agility. Enable Organization with Agile using Tooling/Technology
ARCHITECTING PROJECT MANAGEMENT for Enterprise Agility July 14 to 16, 2016, NIMHANS Convention Centre, Bengaluru Enable Organization with Agile using Tooling/Technology Leverage of Technology Paper Id:
More informationHOW YOUR CAREER BACKGROUND CAN HELP YOU BECOME A BUSINESS ANALYST
By Laura Brandenburg Lesson Objective: After completing this lesson, you ll be able to identify strengths from your career background that will directly support your transition into business analysis.
More informationSession 11E Adopting Agile Ground Software Development. Supannika Mobasser The Aerospace Corporation
Session 11E Adopting Agile Ground Software Development Supannika Mobasser The Aerospace Corporation The Aerospace Corporation 2017 Overview To look beyond the horizon and to embrace the rapid rate of change
More informationLecture 1. Topics covered. Rapid p development and delivery is now often the most important requirement for software systems.
Chapter 3 Agile Software Development Lecture 1 Topics covered Agile g methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods Rapid software development
More informationScrum. a description. V Scrum Alliance,Inc 1
Scrum a description V 2012.12.13 2012 Scrum Alliance,Inc 1 Scrum Principles Values from the Agile Manifesto Scrum is the best-known of the Agile frameworks. It is the source of much of the thinking behind
More informationIntroduction to Agile Change Management
Introduction to Agile Change Management Author Melanie Franklin Director Agile Change Management Limited Introduction Agile change management is a term that is picking up momentum around the world. In
More informationAgile Planning. Petri Heiramo. Agile Coach, CST
Agile Planning Petri Heiramo Agile Coach, CST An Agile Plan Is Not a Rough Guide Some teams think that, if they did not finish all stories, that was OK, we are agile Postponing stories was seen as an acceptable
More informationSoftware Engineering Lecture 5 Agile Software Development
Software Engineering Lecture 5 Agile Software Development JJCAO Mostly based on the presentation of Software Engineering, 9ed Exercise Describe the main activities in the software design process and the
More informationScale agile with the industry s most comprehensive set of agile project and portfolio management capabilities.
Product Tour: CA Agile Central Connect Strategy With Execution Scale agile with the industry s most comprehensive set of agile project and portfolio management capabilities. See how agile products from
More informationJohanna Rothman. Chapter 1 Why Agile and Lean Approaches Work. Copyright 2017
Johanna Rothman Chapter 1 Why Agile and Lean Approaches Work Copyright 2017 Agile and Lean Approaches Why such approaches exist! Software, we have a problem It was thought you could hand a software team
More informationSAP BUSINESS GROUP AGILE FOR SAP SOLUTIONS
SAP BUSINESS GROUP AGILE FOR SAP SOLUTIONS AGILE AND SAP PROJECTS: FINDING THE FIT In a constantly changing business environment, enterprise systems and agile approaches are powerful allies. Enterprise
More informationTitle : Analytics in Agile Project Management Theme: Project Management Leadership > In a Rapidly Changing World Keywords: Agile, Metrics, Analytics, Regression Model Abstract: In the Information revolution
More informationRussell Pannone February 10, 2009
Russell Pannone February 10, 2009 webeagile@aol.com About Me 27 years of System/Software Product Development Experience Developer Data Modeler Team Lead Project Manager Certified Scrum Master/Certified
More informationProject Execution Approach
Project Execution Approach July 2016 2016 Affinity Digital (Technology) Ltd 1 Project Execution Approach Affinity Project Management Affinity is in an excellent position with its multiple methodology offerings.
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 3 Scrum Framework 1 Scrum Origins First mentioned as a development method in 1986, referring to a fast and flexible product development process
More informationOptimizing Scrum-Fall Whitepaper
Optimizing Scrum-Fall Whitepaper Table of Contents Abstract... 2 Our Thinking... 3 A comment on tools for Scrum-Fall... 6 Conclusion... 7 References... 8 1 Optimizing Scrum-Fall Whitepaper Author: Miles
More informationRule = A definition of what a Product Backlog is. Good Practice = A practice which is commonly done and is good to do. Avoid = A practice which, in
Rule = A definition of what a Product Backlog is. Good Practice = A practice which is commonly done and is good to do. Avoid = A practice which, in most cases, is recommended to be avoided. But, for almost
More informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
More informationAgile Software Development in a Regulated Environment. Natalie Custer
Agile Software Development in a Regulated Environment Natalie Custer Disclaimer This presentation represents the understanding of the presenter on the topic addressed. It does not in anyway, form or like
More informationIntroduction. Agile overview. 12 Agile Principles
01 02 03 05 06 08 09 15 20 21 23 25 Introduction Agile overview 12 Agile Principles Agile Development Cycle Advantages & Disadvantages of Agile Top Methodologies Used to Implement Agile Top Methodologies
More informationProcesses and Life- Cycles. Kristian Sandahl
Processes and Life- Cycles Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify
More informationSoftware Design COSC 4353/6353 D R. R A J S I N G H
Software Design COSC 4353/6353 D R. R A J S I N G H Outline Week 2 Software Development Process Software Development Methodologies SDLC Agile Software Development Process A structure imposed on the development
More informationAgile Transformation In the Digital Age
Agile Transformation In the Digital Age 1 Change agile leaders demonstrate five integrated behaviors that, together, create a competitive advantage for the organization. PRESENTED BY: Sridhar Kethandapatti
More informationCTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal
CTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal There are 30 questions on this exam. Each question is worth
More informationFoundations of Software Engineering. Process: Agile Practices Michael Hilton
Foundations of Software Engineering Process: Agile Practices Michael Hilton 1 Learning goals Define agile as both a set of iterative process practices and a business approach for aligning customer needs
More informationIntroduction. Your Software: Faster. Stronger. Better.
Your Software: Faster. Stronger. Better. Introduction The digital age we now live in demands a pace of delivery to market unheard of ever before. Delivering new or enhanced software to market rapidly can
More informationThe Faster Road to Innovation Why Workopolis Went Agile
The Faster Road to Innovation Why Workopolis Went Agile What I m Covering Today Why did we transition to Agile? What we wanted to Achieve Highlights of How We Did It What we Achieved What we Learned Technology
More informationIntroduction to Agile Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016
Introduction to Agile Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016 1 Goals Introduction to Agile Life Cycles The Agile Manifesto and Agile Principles Agile Life Cycles
More informationAgile 101. Brent Hurley Chief Problem Solver Gira Solutions. Values, Principles
Agile 101 Values, Principles and Brent Hurley Chief Problem Solver Gira Solutions @girabrent @GoAgileCamp Core Agile Series Sponsored by For$more$informa+on$on$Agile$Training,$contact:$info@bra6oninc.com$
More informationAgile Surveillance Points
Defense, Space & Security Agile Surveillance Points 2012 NDIA Systems Engineering Conference San Diego, CA Dick Carlson Richard.Carlson2@Boeing.com BOEING is a trademark of Boeing Management Company. Copyright
More informationAgile Software Development:
Agile Software Development: 1.Agile methods 2.Plan-driven and agile development 3.Extreme programming (XP) 4.Agile project management 5.Pair Programming 6.Scrum 7.Scaling agile methods Rapid software development:
More informationBridging the Gap Between Governance and Agility. Mario E. Moreira
Bridging the Gap Between Governance and Agility Mario E. Moreira Approach Success Criteria Senior Management Understanding Helping define what Agile Is and Isn t Adapting Business Governance Establishing
More informationFinancial Management in an Agile World
Financial Management in an Agile World by Beth Lassiter, Michael Noel, and Chris Hess Clear alignment between teams and business objectives is the first step toward streamlining financial accounting. Agile
More informationLecture 8 Agile Software Development
Lecture 8 Agile Software Development Includes slides from the companion website for Sommerville, Software Engineering, 10/e. Pearson Higher Education, 2016. All rights reserved. Used with permission. Topics
More informationProcesses and Life- Cycles. Kristian Sandahl
Processes and Life- Cycles Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify
More informationCraig D. Wilson, MS, PMP, CSM. Matincor, Inc. IT Management Consulting
Craig D. Wilson, MS, PMP, CSM Matincor, Inc. IT Management Consulting IT Management Consultant 10+ years of service as an independent consultant preceded by 10+ years of senior and executive management
More informationAgile Software Development
Agile Software Development Chapter 3 Agile Software Development in the textbook 3.1 Agile methods 3.2 Plan-driven and agile development 3.3 Extreme programming (XP) - A well known agile method 3.4 Agile
More informationChapter 3 Agile Software Development. Part 1b
Chapter 3 Agile Software Development Part 1b 1 Testing in XP Testing is central to XP and XP has developed an approach where the program is tested after every change has been made. XP testing features:
More informationBuilt. for Speed. Agile is helping organizations transform the customer experience and fend off startup disrupters.
Built for Speed Agile is helping organizations transform the customer experience and fend off startup disrupters. BY TEGAN JONES PORTRAITS BY DANIEL BOUD 48 PM NETWORK SEPTEMBER 2017 PMI.ORG Rizwan Khan,
More informationAgile Software Development. Agile Software Development Basics. Principles of the Agile Alliance. Agile Manifesto. Agenda. Agile software development
Agile Software Development T-110.6130 Systems Engineering in Data Communications Software P, Aalto University Agile software development Structured and disciplined, fast-paced Iterative and Incremental
More informationOracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM. An Oracle White Paper April 2012
Oracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM An Oracle White Paper April 2012 OUM Implement Core Workflow White Paper Introduction... 3 OUM is Iterative...
More informationStandard Work and the Lean Enterprise Net Objectives Inc. All Rights Reserved.
Standard Work and the Lean Enterprise 2010 Net Objectives Inc. All Rights Reserved. Lean Thinking Lean Thinking provides foundational principles which involve the entire lifecycle of realizing business
More informationThe Eight Stages of an Agile Approach That Works
The Eight Stages of an Agile Approach That Works An Overview of the OutSystems Approach to Agile Introduction With the experiences gathered through 500+ Agile projects, the OutSystems team has developed
More informationScrum for Services. Scrum Day MN, October 2018 Jay Blog: travelerspants.com
Scrum for Services Scrum Day MN, October 2018 Jay Halliday @hallydally Blog: travelerspants.com Expectations Intro Engineering Scrum implementation history Scrum for Services Benefits / Struggles of Scrum
More informationThe agile journey at Danske Bank. Anders Peter Lange and Mikkel Toudal Kristiansen
The agile journey at Danske Bank Anders Peter Lange and Mikkel Toudal Kristiansen A little bit of background Why did we start this journey Danske Bank is more than 100 years old many things are still very
More informationAGILE LESSONS FROM THE NEW PMBOK. Presented by Eddie Merla, PMI-ACP, PMP
AGILE LESSONS FROM THE NEW PMBOK Presented by Eddie Merla, PMI-ACP, PMP 2 Agenda Summary of Changes Agile Concepts Five Mindset Shifts Agile Methods & Scrum Q&A Wrap-up 3 Summary of Changes Project managers
More informationProject Management in Practice Agile Agile 101 Introduction to Agile
101 Introduction to 7-1 Introduction Overview Brief History of Methodologies vs. Traditional PM 7-2 Introduction 7-3 After today s session, you ll walk away with: An understanding of what means in the
More informationAdvice on Conducting Agile Project Kickoff. Meetings
Advice on Conducting Agile Project Kickoff by Mike Cohn 12 Comments Meetings Advice Image not found on Conducting or type unknown Agile Project Kickoff Meetings A traditional project manager who was in
More informationSage North America, Mid-Market R&D. One Team s Agile Journey
Sage North America, Mid-Market R&D One Team s Agile Journey Darrick Coles Director, R&D Sage 500 ERP darrick.coles@sage.com twitter: @dbc_ca Education BS Computer Science, University of Illinois MBA, finance,
More informationIntroduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
More informationThe Product Manager s Guide to Strategic Planning
The Product Manager s Guide to Strategic Planning Table of Contents 1. Why You Need to Start with Top-Down Strategic Planning 2. Developing the Product Strategy 3. Defining Your Product Goals 4. Roadmap
More informationFIT2101 Software Engineering Process and Management
FIT2101 Software Engineering Process and Management Agile and Software Process Models Topics Covered Features of Agile What Agile Isn t Agile Process Models Software Process Models In 2001 leaders of lightweight
More informationManage Projects Effectively
White Paper Application Development, Test & Delivery Manage Projects Effectively Table of Contents page Executive Summary... 1 The Micro Focus Solution Invest in What Matters Most then Manage It... 2 Strategic
More informationSprint. Innovate via rapid product/service prototyping and market testing.
Strategic Doing Google Ventures Sprint SCRUM Kanban Lean Development Guiding Themes Align networks in via a shared discipline of simple rules. Innovate via rapid prototyping and market testing. Empower
More informationQ&A from Transitioning from Waterfall to Agile Web Seminar
Q&A from Transitioning from Waterfall to Agile Web Seminar -How does this method allow you to provide the client with a budget that they can depend on at the start of the project? ASK: Because the Agile
More informationAn Agile Projects Introduction Course #PMCurrent-1
An Agile Projects Introduction Course #PMCurrent-1 Aaron MacDaniel, PMP, CSM, MBA Lead Instructor - BetterPM.com An Innate Images, LLC Company 1 Course Agenda About BetterPM.com A typical Waterfall Project
More informationProduct Owner - The Single Wring Able Neck
Product Owner - The Single Wring Able Neck by Jens Ostergaard Certified Scrum Product Owner 1 What is Scrum? Product Owners determine what needs to be built in the next 30 days or less. Development Teams
More information6 PERSPECTIVES OF A LEADER
6 PERSPECTIVES OF A LEADER Your leadership effectiveness is determined by two things: the decisions you make and the influence you have. Great leaders are able to make exceptional decisions. They have
More informationIntroduction to Agile/Extreme Programming
Introduction to Agile/Extreme Programming Matt Ganis, Senior Technical Staff Member (Certified Scrum Master) IBM Hawthorne, New York ganis@us.ibm.com August 2007 Session 8061 Current slides at: http://webpage.pace.edu/mganis
More informationHow to Run Agile Development for SAP
How to Run Agile Development for SAP Are you giving your business what it really wants? Or do you have a : ( business In many business who run SAP expectations of IT have flat lined and there s a general
More informationScaling Agile With ZolonTech. Transform your Organization today with Agile Application Development
Scaling Agile With ZolonTech Transform your Organization today with Agile Application Development ABSTRACT AGILE DEVLOPMENT To face many of the challenges and frustrations around slow and unproductive
More informationAchieving Balance: The New Pivotal Points of Software Development
White Paper Software Delivery & Testing Achieving Balance: The New Pivotal Points of Software Development A rational model of software is to design it quickly; the economic pressure to improvise presents
More informationAgile for Hardware Development
Agile for Hardware Development. Agile for Hardware Development PLAYBOOK PLAYBOOKHQ.co Contents Background Agile Manifesto Agile Values Cost of Delay Agile Principles Agile Methods Conclusion 3 4 6 7 9
More informationBusinesses now operate in rapidly changing environment.
Computers II Lesson 3 3.0 Agile software development Businesses now operate in rapidly changing environment. They have to respond to new opportunities and markets, changing economic conditions, and the
More informationA philosophy first and methodology second
Demystifying Agile A philosophy first and methodology second Authors: Jonathan McAllister Page 1 WHERE AGILE CAME FROM In 2001, a group of well-known software industry pundits converged on the small town
More informationTraining Your Customer
Training Your Customer Petri Heiramo Agile Coach, CST 1 We Are Looking at How our customers can benefit from Agile How we can get customers understand Agility and its benefits How can we help them to be
More informationWelcome. #AdvanceYourPotential
Welcome #AdvanceYourPotential Name tags Today Todays photos are available on Instagram. Feel free to say no. Live stream experiment. Thank you to Ampersand International and Laura Frazer. Thank you to
More informationOur Approach to the Scaled Agile Framework (SAFe )
ESSENTIAL WHITE PAPERS Our Approach to the Scaled Agile Framework (SAFe ) by Al Shalloway Our Approach to the Scaled Agile Framework (SAFe ) by Al Shalloway A Net Objectives Essential White Paper Net Objectives
More information8 th of April 2015 Bucharest, Romania Vlad Gabriel Sorin Agile PM/Scrum Master
8 th of April 2015 Bucharest, Romania Vlad Gabriel Sorin Agile PM/Scrum Master 1. Introduction 1 min. 2. Waterfall vs Agile 5 min. 3. Agile - General Concepts 5 min. 4. Agile methods: Scrum vs XP vs Lean
More informationHandling Product Management Across The Enterprise. copyright Net Objectives, Inc.
Handling Product Management Across The Enterprise copyright 2010. Net Objectives, Inc. Lean for Executives Product Portfolio Management Business Lean Enterprise ASSESSMENTS CONSULTING TRAINING COACHING
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 7 Agile Methodologies: Scrum 1 Agile Methodologies: Brief History First appeared in 1995. The once-common perception that agile methodologies
More informationCS 5704: Software Engineering
CS 5704: Software Engineering Agile Methodologies Dr. Pardha S. Pyla 1 1 What is wrong with this? System requirements Software requirements Analysis Program design 1. Rigid/heavy weight process 2. Too
More information7 Ways to Accelerate Your Go-to-Market Initiatives
7 Ways to Accelerate Your Go-to-Market Initiatives Go on, admit it: it s getting harder and harder to keep up with the speeds at which we are required to do business. Our business cycles are getting faster
More informationSOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and
More informationOwning An Agile Project: PO Training Day 2
Owning An Agile Project: PO Training Day 2 Petri Heiramo Agile Coach, CST Product Management PO Product management is a larger scope than what Scrum defines as a PO Or rather, Scrum implicitly assumes
More informationContents. Acknowledgments Preface What You ll Find in This Book How to Use This Book
Contents Acknowledgments Preface What You ll Find in This Book How to Use This Book vii ix x xi Chapter 1 Introduction 1 So, What Is It? 4 Why Does It Matter? 5 How You Can Use It 9 Chapter 2 The Business
More informationTHE ESSENCE OF AGILE. Embracing Agility Means Agility by the Business, for the Business
THE ESSENCE OF AGILE Embracing Agility Means Agility by the Business, for the Business Author By Nidhi Srivastava Global Head, Consulting Practices, Tata Consultancy Services The push for agility in software
More informationSystem Development. Software Project Management Triangle Waterfall Model V-Model Agile Development User Acceptance Test Minimum Viable Product
System Development Software Project Management Triangle Waterfall Model V-Model Agile Development User Acceptance Test Minimum Viable Product https://twitter.com/ultralinx/status/605677796074106880/photo/1
More informationBeing Agile at a Small Agency How to Apply Agile Principles in a Not-So-Iterative Environment
Being Agile at a Small Agency How to Apply Agile Principles in a Not-So-Iterative Environment Mark Wahl Technical Director, Jake Group @markawahl May 31, 2017 Getting Started A small, growing agency is
More information2. True or false: In Scrum all the requirements for the project are known prior to the start of development.
CTC-ITC 310 Program Management California State University Dominguez Hills Fall 2018 Instructor: Howard Rosenthal Assignment 5 A Deeper Look At Agile Methodologies Answer Sheet Each question is worth 10
More informationAgile Certified Practitioner (ACP) Exam Prep Course 7 Adaptive Planning
Agile Certified Practitioner (ACP) Exam Prep Course 7 Slide 1 Slide 2 Domain Tasks Levels of Planning 1. Plan at multiple levels (strategic, release, iteration, daily) creating appropriate detail by using
More informationScrum. Software Engineering and. The Waterfall model. The Waterfall model - some arguments. The Waterfall model - some arguments. Time.
Software Engineering and Scrum autumn 2010 Department of Computer and Information Science Linköping University, Sweden The Waterfall model Requirements One of the first life-cycle models (Royce, 1970)
More informationSoftware Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000)
Software Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000) armahmood786@yahoo.com alphasecure@gmail.com alphapeeler.sf.net/pubkeys/pkey.htm http://alphapeeler.sourceforge.net
More informationSTOP. COLLABORATE & LISTEN. EIGHT BEST PRACTICES FOR IMPROVING COLLABORATION IN THE PROPOSAL PROCESS
STOP. COLLABORATE & LISTEN. EIGHT BEST PRACTICES FOR IMPROVING COLLABORATION IN THE PROPOSAL PROCESS THE NEED TO COLLABORATE The saying, it takes a village, is certainly true for many things, but it seems
More informationBecome A Change Champion
Become A Change Champion By Mark Williams Head Of Training MTD Training Web: www.mtdtraining.com Telephone: 0800 849 6732 1 MTD Training, 5 Orchard Court, Binley Business Park, Coventry, CV3 2TQ Web: www.mtdtraining.com
More information