When you start building reusable assets there is considerable awkwardness with trying to align your reuse strategy with iteration goals. The real challenge is when you are not sure about refactoring existing assets. You will discover hidden couplings to implementation technology or platform, undocumented assumptions about how something will work, and all kinds of duplications sprinkled across your codebase. Soon, you will find yourself asking the questions such as – What can we reuse? Didn’t we just solve the same problem? Is this reusable as-is or needs to be refactored?
I just finished reading a short book on applying lean prinicples to software development. As we are following the scrum methodology for developing software products witihn our team I was just wondering how this methodology perfectly fits into the lean prinicples effortlessly. Thought I should blog about this to illustrate the Lean prinicples coming to life in the SCRUM methodology of software project management. Prinicple of Flow: According to the flow prinicple, people involved in producing a product work hand in hand without creating intermediate buffers. hey work on one piece at a time, producing a finished part with the minimum throughput time. World of Scrum : A prioritized backlog is maintained from which the team picks up one item, finishes it completely with testing and documentation and releases the feature at the end of sprint .
Agile and the Fine Art of Gathering Application Requirements Bloated enterprise systems are taking more time and money without providing what organizations really need. Learn how Agile methods can help.
Just because your requirement is not a user story does not mean you have to throw it out when planning your next sprint. See one way (that is working) for managing non-functional requirements with an agile team. Product Backlog Stories Every article* I can remember reading that explains how to manage a product backlog talks about user stories. Those articles are necessary, but not sufficient . You’ll create better products by developing them from the outside-in, with a user-centric point of view.
User Stories are one of the key agile artifacts for helping implementation teams deliver the most important capabilities first. They differ from use cases in some important ways, but share more commonalities than you might think. User Stories Applied
Eskander Matta This man says, “No.” So what? He may look a little nerdy but he is a Senior Vice President at Wells Fargo Bank and using agile development techniques, he has dramatically reduced the time to develop new products for Wells Fargo’s online business. What’s the big deal?
I have taught project management courses at the University of Wisconsin-Milwaukee since 2002. While I teach 'traditional,' process-oriented PM classes, I recently started teaching an "Introduction to Agile" course that I have now delivered twice. The course is a 2-day overview of Agile concepts and methods - students are introduced to the Agile Manifesto, a brief history of the "movement," overviews of Agile methodologies such as Scrum, XP, and Unified Process, and comparisons to waterfall/traditional process-oriented methods.