Architecture Envisioning: An Agile Best Practice A common agile practice is to perform some high-level architectural modeling early in the project to help foster agreement regarding your technical strategy within the team and with critical stakeholders. The goal at this point is to identify an architectural strategy, not write mounds of documentation, enabling you to do this swiftly. You will work through the design details later during development cycles in model storming sessions and via TDD. This article addresses several critical questions: 1.
DFW Scrum (Irving, TX) Welcome to DFW Scrum! Our goal is to help you do better today than you were doing yesterday. The best way to do that is through the collective wisdom and experience of the crowd (sprinkled with some industry experts). Scrum is very simple to understand, but very hard to implement as it takes your problems and throws them in your face each and every day. We consider ourselves an organic group that is designed to tackle the challenges and issues you face regardless of your role in Scrum. Mike Cohn Mike Cohn, 2013 He has served as Vice President of Development at four different companies that successfully employed agile concepts and strategies and been a technology executive in companies of various sizes, from start-up to Fortune 40. Cohn is the author of Agile Estimating and Planning, User Stories Applied for Agile Software Development and Succeeding with Agile: Software Development using Scrum, as well as books on Java and C++ programming and articles for Better Software, IEEE Computer, Software Test and Quality Engineering, Agile Times, Cutter IT Journal, and the C++ Users' Journal. He is also the editor of the Addison-Wesley Mike Cohn Signature Series of books. Cohn was a Keynote Speaker on ADAPTing to Agile for Continued Success at the Agile 2010 Presented by the Agile Alliance. In 2012, Cohn was named #1 in The Top 20 Most Influential Agile People.
Agile Community Content on InfoQ Research on Agile What are the most widely used .NET practices and tools? This InfoQ Research item examines the adoption level of a range of practices and tools that aim to assist .NET developers in these practices. Note that we have focussed only on these practices - there are other tools such as reflectors, productivity tools, frameworks etc. which we are not covering in this research. Biggest Impediments for Effective Agile Adoption?
Scrum (development) Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Each sprint is started by a planning meeting.
Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise The Disciplined Agile Delivery (DAD) process framework, as described in this book, is a hybrid approach which extends Scrum with proven strategies from Agile Modeling (AM), Extreme Programming (XP), and Unified Process (UP), amongst other methods. DAD extends the construction-focused lifecycle of Scrum to address the full, end-to-end delivery lifecycle from project initiation all the way to delivering the solution to its end users. The DAD process framework includes advice about the technical practices purposely missing from Scrum as well as the modeling, documentation, and governance strategies missing from both Scrum and XP. More importantly, in many cases DAD provides advice regarding viable alternatives and their trade-offs, enabling you to tailor DAD to effectively address the situation in which you find yourself.
Agile Techniques: Getting Started With Kanban As agile software development methodologies become more familiar within mainstream IT organizations, agile practitioners have been experimenting with some of Agile's Lean roots. One lean practice that has gained traction with many agilists is a Kanban board. Lean has much in common with agile. Lean has two principles, add value for your customer and empower your workers. If we look at the Agile Manifesto's 4 we can see similarities between the manifesto and Lean principles: [login] Henrik Kniberg's blog I debug, refactor, and optimize IT companies. And jam alot too. Spotify Engineering Culture (part 1) March 27, 2014 – 10:12 am
Scrum Effort Estimation and Story Points Posted by admin under Scrum Basics In waterfall, managers determine a team member’s workload capacity in terms of time. That is, managers estimate how long they anticipate certain tasks will take and then assign work based on that team member’s total available time. This is problematic because it does not distinguish between a story that is very hard to complete and one that is undemanding; it only considers how long the work will take. UML 2 Activity Diagrams: An Agile Introduction UML 2 activity diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the detailed logic of a business rule. Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so that it is simple enough that you don't require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of flow charts and data flow diagrams (DFDs) from structured development.
Agile Alliance Group News Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.