how Kanban metaphor from Lean manufacturing and the Feature Injection template play into Behaviour Driven Development, working together to help us identify the most important software, reduce unnecessary artifacts at each stage of development, and produce the minimum necessary to achieve a vision
InfoQ article: "Pulling Power: A New Software Lifespan" - 0 views
-
-
The artifacts signal each role to create further artifacts until the vision is implemented and the business value is earned
-
"Generating reports," he says, "is like lead. It's easy to work with, and it's cheap. It's also heavy, worthless, and drags you down. Developers sink a lot of time into writing report software. Why? Buy it, install it, hack it so it works. Use Excel. Don't spend money writing report software, unless you're the kind of company that sells them to other companies.
How Google Sold Its Engineers on Management - 0 views
-
A good manager: 1. Is a good coach 2. Empowers the team and does not micromanage (See the sidebar “How Google Defines One Key Behavior”) 3. Expresses interest in and concern for team members’ success and personal well-being 4. Is productive and results-oriented 5. Is a good communicator—listens and shares information 6. Helps with career development 7. Has a clear vision and strategy for the team 8. Has key technical skills that help him or her advise the team
-
Employees with high-scoring bosses consistently reported greater satisfaction in multiple areas, including innovation, work-life balance, and career development
-
high-scoring managers saw less turnover on their teams than the others did—and retention was related more strongly to manager quality than to seniority, performance, tenure, or promotions
- ...1 more annotation...
Alistair.Cockburn.us | Are iterations hazardous to your project? - 0 views
-
Simply using iterations, user stories and velocity doesn’t mean your project is agile – or on the way to success.
-
why “iterations” may be hazardous to your project: ‘’Danger grows when the results of the iteration are not directly linked to delivering the product to the end user.’’ Without that linkage, iteration results hang in the air
-
What gets in the way is that the project is set up as a pipeline, with programming put somewhere in the middle of the pipeline. In this project setup, there is really nothing the programmers can do to show how their work connects to deliveries, because there are work stations before and after theirs. All they can report is that “some new code is integrated into the code base.” They are doing incremental development but not agile development.
- ...6 more annotations...
2014 DevOps Report | Puppet Labs - 1 views
Distributed Agile Development - 0 views
Managing WIP isn't the same as Limiting WIP: Part 1 - 0 views
-
To determine the truth of this we only need to look at the feature sets of the popular tools for managing eXtreme Programming and Scrum such as Rally, VersionOne, ScrumWorks, Mingle and very new tools like Borland Team Focus, to discover that not a single one of these tools allows you to set an explicit WIP limit. None of them provide a pull signal to start new work. Very few of them are even capable of reporting the quantity of work-in-progress.
-
s we learned more about the value of managing WIP, we introduced concepts to encourage and enable it, such as the use of Cumulative Flow Diagrams (a.k.a. Burn Up charts)
-
Agile teams encountering an impediment would generally mark a story as blocked and go on to another one
- ...2 more annotations...
Challenging Why (not if) Scrum Fails | NetObjectives - 0 views
-
I do believe for Scrum to work beyond the team you need more than Scrum
-
what to add to Scrum making it more effective when it won't readily work
-
lack of team agility is not always the major impediment to Enterprise Agility
- ...12 more annotations...
Agile PMO Role - 0 views
-
Institute an agile transition team, and have the agile PMO play a significant role on that team. If you are starting on the journey, establishing an agile transition team can be a critical factor in your success. The agile transition team plans and implements the strategy for the organization’s agile transition (using a backlog, iterations, planning meetings, retrospectives and, in general, responding to change) This group monitors and communicates results throughout the organization, and is responsible for removing organizational level impediments. The PMO representative can act as ScrumMaster for the agile transition team. Members should be leaders representing different departments and functions that are impacted by the agile transition. For example, having leaders from development, QA, product development and the PMO is an excellent practice.
-
Establish a “Meta Scrum” that is tasked with mapping projects and features to corporate strategy. As part of optimizing the whole, it is important for there to be a big picture view across products and features. In general, product managers are tasked with defining, prioritizing and communicating the vision and features for their products. When you have a program that encompasses multiple products with multiple product owners and project teams, keeping everything in line with the corporate vision can sometimes be overlooked. Unlike the Scrum of Scrums--which is tactical, i.e. focused on execution--the Meta Scrum is focused on the strategic planning and decisions guiding the program or programs as a whole. Establishing a Meta Scrum with the PMO representative acting as ScrumMaster to plan and facilitate meetings (as well as reporting and tracking decisions and action items) can add significant value in having a program able to rapidly respond to change while staying true to the corporate strategy and objectives.
-
I like using story points to establish the velocity of individual teams. From a program point of view, however, story points are difficult to use across multiple teams. The nut there is that one team’s story point is not equivalent to another team’s story point. To crack that nut, I use agileEVM to “normalize” to standard project management metrics like the Cost Performance Index and the Schedule Performance Index, as well as the Estimate At Complete in integrated dollars. These metrics can be aggregated across teams to establish progress against the plan for the entire program.
- ...1 more annotation...
InfoQ: Opinion: Agile Coaches Frequently a Source of Adoption Problems - 0 views
-
Coaches help teams learn Agile practices get from 'Agile seems to be something we should do' to 'we are practicing Agile development and succeeding by regularly delivering business value'.
-
ncreasingly there are reports of initial success followed by failures with Agile adoption.
-
I believe that there is a problem to how current Agile coaches - especially external ones (such as the author) - have traditionally performed their jobs. In fact, I think we are part of the problem
- ...2 more annotations...
From the Agile Transformation Trenches: Borland Agile Assessment 2009 - 1 views
-
We measure progress in business-valued terms such as time-to-value, cost/benefit ratio and customer satisfaction.
-
There is no "score" to this assessment. It is administered anonymously with results reported in aggregate. This is a diagnostic tool to help us all reflect on our processes and identify ways to improve. It cannot measure "improvement" from a previous assessment, only relative importance of potential improvements to our current situation.
-
inally, this is not a competition. The results will be most useful in helping you reflect on your current circumstances and establish priorities within your teams on areas of potential growth.
Creating an Agile Culture to Drive Organizational Change - 1 views
-
It is critical that everyone has the same understanding of, and commitment to, the desired outcome: a business that is reliable through predictable technology processes that deliver business agility. To do this, there needs to be a management commitment to develop a focused, on-going practice around the pursuit of organizational maturity. As part of this, gaps in skills and capabilities should be identified and positive action – training, coaching, process improvement and tools deployment – taken in order to close the gap
-
the work force needs to understand the business drivers for Agility. They need to be challenged to improve their quality, improve their cycle times, to improve the frequency of releases and the value they deliver to the customer. They need to know how these things fit within the bigger picture and why improvement is their responsibility.
-
To change a culture it's important to recognize that every knowledge worker makes decisions and takes actions that affect the performance of the business. The culture in the organization is the reflection of those decisions and actions.
- ...14 more annotations...
Scrum Log Jeff Sutherland: The Managers Role in Scrum - 1 views
-
managers handle 'external stuff' to the team
-
ontract negotiations and procurement.
-
he role that a line manager plays in an employee's personal and professional development, often in the form of coaching or assisting in HR-related issues
- ...11 more annotations...
1 - 14 of 14
Showing 20▼ items per page